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

No annotations are provided, so the description carries the full burden. It does disclose one behavioral trait—'Key discarded'—indicating the input is not retained. But it says nothing about side effects, return values, error behavior, or why the schema contains many unrelated parameters.

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 exceptionally short—two sentences with no filler. 'Key discarded' is a meaningful privacy note. However, the brevity borders on under-specification because critical operational details are absent.

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 optional parameters, no output schema, and no annotations, this description is inadequate. It does not explain what the tool returns, which parameter to populate, what 'shape' means precisely, or how this differs from other shape tools beyond the name.

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 description coverage is 100%, so a baseline of 3 applies. The description adds no parameter-specific meaning, and more importantly, it fails to link the Jira key concept to any of the nine parameters. The parameter descriptions are generic about the data type, not about the shape check, leaving selection 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 and resource: 'Check a Jira issue key shape.' This clearly distinguishes it from sibling shape-checking tools like domain-shape or figma-url-shape. However, it does not identify which of the nine schema parameters should carry the Jira key, leaving the operational target ambiguous.

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?

Usage is only implied by the tool's name and first sentence. There is no guidance on when to prefer this tool over other shape-checking siblings, nor any mention of what types of inputs are appropriate. With many similar sibling tools, the lack of explicit routing is a significant gap.

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