Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the transparency burden, but it only says 'Key discarded' and does not disclose return values, side effects, or whether the tool performs any validation beyond shape. The parameter descriptions inconsistently mention discarding/no disk access, which adds confusion rather than clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the main action, but it is too minimal to be useful. It omits essential details such as accepted key format and return behavior, so the brevity does not compensate for the lack of substantive content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description leaves critical context undefined: what constitutes a valid Jira key shape, what the tool returns, and how the key is supplied. The unrelated input schema deepens the incompleteness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is 100%, each parameter description appears copied from unrelated tools (e.g., 'Git ref name', 'HTTPS URL to normalize or cite', 'IANA timezone name'). None of them explain how to provide a Jira issue key, so they actively mislead instead of clarifying the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific check ('Jira issue key shape'), but the input schema exposes no 'key' parameter, instead listing unrelated fields like url, city, json, and query. This mismatch makes the stated purpose misleading and hard to map to the actual interface.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given for when to use this tool versus sibling shape/check tools such as github-repo-shape, figma-url-shape, or wiki-title-ok. There are no usage conditions, examples, or alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.