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

The description discloses that the key is discarded, and each parameter description repeats 'discarded after the check/call', indicating no side effects. However, it does not disclose what constitutes a valid shape, what the return value is (boolean, error message, etc.), or how non-Jira inputs are handled. Without annotations, the description carries the burden but only partially addresses it.

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 extremely concise (two sentences), which is structurally efficient, but it is under-specified for a tool with nine parameters. The brevity does not compensate for the lack of essential information about scope and behavior.

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?

With nine parameters, no output schema, and no annotations, the description is severely inadequate. It does not explain what shapes are validated, how the tool handles different input types, what it returns, or how it differs from siblings. An agent cannot safely call this tool without further information.

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?

Schema coverage is 100%, so the baseline is 3, but the parameter descriptions are inconsistent with the tool's stated purpose—for example, 'url' is described as 'HTTPS URL to normalize or cite' rather than a Jira key shape check. The descriptions add no meaning about what 'shape' means for each param and are confusingly copied from other contexts. The tool description itself adds nothing to clarify the params.

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 verb and resource ('Check a Jira issue key shape'), but the input schema contains nine parameters (ref, url, city, feed, host, json, path, zone, query) that are unrelated to Jira keys, with descriptions referencing URL normalization, weather hints, and JSON validation. This mismatch makes the purpose misleading—an agent would not know what the tool actually checks or how to select it among sibling shape tools like domain-shape or github-repo-shape.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention that it accepts various input types or that it might be a generic shape checker. An agent cannot infer when to prefer jira-key-shape over sibling tools like domain-shape or validate-json.

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