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

No annotations are present, so the description carries the burden of behavioral disclosure. It does disclose that the key is discarded, but it says nothing about the return value, whether any external lookup occurs, or how invalid shapes are handled. This is minimal transparency beyond the schema's per-parameter discard notes.

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?

Two short sentences with no filler, and the main action is front-loaded. The privacy note is compact and does not repeat the schema at length. This is appropriately concise for the limited content it provides.

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?

There is no output schema, so the description should explain what the tool returns, but it does not. It also fails to tie the Jira key to any of the seven input properties, making the tool difficult to invoke correctly. The schema's property descriptions are helpful but do not compensate for these two critical gaps.

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?

The input schema has descriptions for all 7 properties, so schema coverage is high and the baseline is 3. The description adds no parameter-level meaning and uses the term 'key' without mapping it to any of the declared properties, leaving ambiguity about where the Jira key should be provided.

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?

States a specific verb and resource: 'Check a Jira issue key shape.' The Jira qualifier distinguishes it from sibling shape tools. However, it doesn't explain what result is returned or which input carries the key, so the purpose is clear but not fully actionable.

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 on when to use this tool versus sibling shape tools, nor any prerequisites or exclusions. The only usage signal is the implied Jira context from the name and description, which is not enough for reliable tool selection.

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