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

No annotations are provided, so the description must disclose behavior. It only says 'Key discarded,' which is ambiguous and does not clarify side effects (e.g., whether it makes network calls, whether it is read-only, or what happens to the other 8 parameters). It fails to disclose the tool's operational impact.

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 at two sentences, but it under-specifies. Conciseness is appropriate when content is sufficient; here it omits essential details, making it more an under-specification than effective brevity.

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 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what 'shape' means, what the return value is, or how to construct a valid call. For a validation tool, this is wholly inadequate.

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?

While schema coverage is 100%, the parameter descriptions are generic and do not relate to Jira keys. The tool description adds no mapping from parameters to the tool's purpose; it does not say which parameter is the key or how the others are used. The mismatch between the tool name and the parameter set confuses rather than clarifies.

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 verb and resource ('Check a Jira issue key shape'), but it is vague about which input is the key. The schema has 9 unrelated parameters (city, feed, host, zone, query) with no 'key' field, so an agent cannot determine what to pass. It does not distinguish from sibling shape-checkers like github-repo-shape or domain-shape beyond the Jira-specific name.

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 vs alternatives. The description does not mention that this is for Jira key validation, nor does it name sibling tools or conditions for choosing this one. An agent has no basis to select it over other shape-checkers.

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