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

No annotations are provided, so the description carries the full burden, but it only offers the terse 'Key discarded' note. It does not disclose return values, error behavior, whether network access is required, or any side effects beyond discarding input.

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 very short and front-loads the purpose, with no filler. However, it is under-specified: one additional sentence clarifying which parameter carries the Jira key would make the definition appropriately sized.

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 no annotations, no output schema, and a seven-parameter schema that never names a key field, an agent cannot determine how to invoke the tool or interpret its result. The definition is critically incomplete for a callable validation tool.

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?

Every parameter in the input schema has a description, giving high schema coverage, but none of the parameters is identified as the Jira key the tool is meant to check. The description adds no mapping from 'key' to any actual field, making invocation semantically ambiguous.

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 action ('Check') and resource ('a Jira issue key shape'), and adds that the key is discarded. However, it nearly restates the tool name and does not differentiate it from sibling shape validators like github-repo-shape or domain-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 the sibling shape-checking tools, nor any conditions under which it should be avoided. The description provides no prerequisites, expected input format, or exclusions.

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