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

With no annotations provided, the description carries the full burden of disclosing behavior. The only behavioral hint is 'Key discarded,' which suggests the input is not retained, but it does not state whether the operation is read-only, what happens to other parameters, whether it makes network calls, or what the response format is. The description is far too sparse to convey the tool's actual behavior.

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 only two short sentences, which is extremely concise, but it is under-specified rather than efficiently concise. While the purpose is front-loaded, the lack of necessary detail (which parameter, what 'shape' means, return value) makes the brevity counterproductive. It does not earn its place because it leaves critical information out.

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 9 optional parameters, no output schema, and no annotations, this description is wholly inadequate. It provides no information about the expected input, the nature of the check, the return value, or any side effects. An agent cannot call this tool correctly without further investigation. It fails to cover even the most basic contextual needs.

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 the schema already documents all 9 parameters. The description adds no parameter-specific meaning beyond the schema, and it fails to connect the purpose ('Jira issue key') to any specific parameter. Since coverage is high, baseline is 3; the description neither enhances nor contradicts the schema, but the missing linkage is a notable gap.

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 verb (check) and resource (Jira issue key shape), which is not a tautology. However, it does not specify which of the 9 parameters holds the key, nor does it clarify what 'shape' entails (e.g., format validation like ABC-123). It also does not distinguish this from sibling shape-check tools (domain-shape, github-repo-shape), leaving the agent uncertain about which tool fits.

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 any alternative. The description does not mention context, prerequisites, or exclusions. An agent would have no idea whether to pick this over similar shape-check tools or when to avoid it.

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