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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says 'Key discarded,' which hints at lack of retention, but it does not explain what happens on valid or invalid shapes, what the return value looks like, or why several schema parameters are marked as discarded. This is too little context to guide a call.

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 short, but this is under-specification rather than effective conciseness. The two sentences omit the mapping to actual input parameters and the success/failure behavior, so they do not sufficiently inform an agent.

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 a seven-parameter schema, no annotations, and no output schema, the description is far from complete. It does not explain which parameter carries the Jira key, what a valid shape is, or what the tool returns, so an agent cannot safely invoke it correctly.

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 schema documents seven parameters with individual descriptions, but none of them is a 'key' and the description does not map any parameter to the Jira-key check. The mismatch between the 'key' concept and the provided ref/url/city/etc. parameters makes the parameter semantics more confusing rather than clearer.

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 verb and a resource ('Check a Jira issue key shape'), but it largely restates the tool name and introduces a 'key' that does not appear anywhere in the input schema. An agent cannot tell which input should be checked, so the purpose is not functionally clear despite the grammatical sentence.

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 is given on when to use this tool versus the many sibling shape/URL/domain checkers. There are no conditions, exclusions, or references to alternatives, so choosing this tool over siblings would have to be based on the name alone.

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