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

With no annotations provided, the description carries some behavioral burden. 'Key discarded' suggests the key is not retained or returned, which is a useful privacy/behavioral signal, but it is ambiguous and does not disclose side effects, output, or error 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 very short and front-loaded with the main action. The second sentence 'Key discarded' is cryptic but not verbose, so the overall structure is compact; clarity is the main weakness rather than conciseness.

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 and no explanation of what a shape check returns (e.g., boolean or validation message), and the schema/tool mismatch is left unresolved. The description is too incomplete to allow reliable invocation or result interpretation.

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 contains nine unrelated optional string parameters (ref, url, city, feed, host, json, path, zone, query), and none of them maps clearly to a Jira issue 'key'. Despite 100% schema-description coverage, those descriptions do not connect to the tool's stated purpose, so an agent cannot determine what value to pass.

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 ('Check') and a specific resource ('Jira issue key shape'), so the core purpose is identifiable. It does not explicitly differentiate from sibling shape-checking tools, but the name and stated object make the intent reasonably clear.

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 explicit guidance on when to use this tool instead of the many sibling validation/shape tools. Usage is only weakly implied by the tool name and description, with no context, exclusions, or alternative suggestions.

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