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

No annotations are provided, so the description carries the transparency burden. It does disclose that the key is discarded, implying non-persistence, but it does not say whether the check is local, what it returns, how invalid shapes are handled, or whether any side effects exist beyond discarding the 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 two short sentences with no filler. It front-loads the main purpose and then adds a useful behavioral note. Every word earns its place.

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 and no output schema, the description needs to explain how to invoke the tool and what result to expect. It instead leaves a broad nine-parameter schema, never identifies the parameter for the Jira key, and never states the return value or validation behavior. This is not complete enough for confident correct invocation.

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 has 100% parameter descriptions, none of the nine properties is named 'key' or described as a Jira issue key. The description's 'Key discarded' does not map cleanly to any schema property, leaving the agent uncertain which argument to pass. High schema coverage is undercut by the mismatch between the tool's purpose and the actual parameters.

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 verb and object: it checks the shape of a Jira issue key, and it adds that the key is discarded. This is clear enough to identify the tool's core purpose, though it does not distinguish it from sibling shape-checking tools or define what shape means.

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 about when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. The only contextual hint is the name and the sentence, so an agent is left to infer appropriate usage.

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