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

No annotations are present, so the description carries the full burden for side effects and return behavior. 'Key discarded' hints that input values are not retained, but the tool does not disclose whether it returns a boolean, throws, or otherwise behaves, and it says nothing about the other eight schema fields.

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 admirably short and front-loaded, with no filler. But it is under-specified for a tool with nine parameters: 'Key discarded' is cryptic, and no example or expected pattern is given, so brevity begins to cost clarity.

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?

For a tool with nine parameters, no output schema, and no annotations, the description is not complete enough for reliable invocation. An agent is left without the expected Jira key pattern, the parameter to use, and the result contract; the schema mismatch makes the gap severe.

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 the schema provides descriptions for all nine fields, none of them is a Jira issue key, and the description never maps 'key' to a parameter. The high schema coverage therefore does not help an agent select the correct input; the description adds no parameter-level meaning.

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 names a specific action and resource: checking the shape of a Jira issue key, and this distinguishes it from sibling shape/validation tools such as github-repo-shape or domain-shape. However, it never defines what the accepted key shape is, and the supplied schema contains no 'key' parameter, which undermines clarity.

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 instead of alternatives, no exclusions, and no mention of related tools. The only implied context is 'check a shape,' but no sibling differentiation is provided.

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