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

There are no annotations, so the description carries the full burden. 'Key discarded' is a useful disclosure that the input is not retained, which is a meaningful privacy-related behavior. However, it does not describe whether the tool returns a boolean, throws on invalid shapes, makes network requests, or has any other side effects. The behavioral disclosure is minimal.

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. The purpose is front-loaded and 'Key discarded' adds a behavioral detail without unnecessary verbosity. 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?

The tool has no annotations and no output schema, and the input schema is large and unrelated to the stated Jira-key purpose. The description does not explain the expected Jira key format, the return value, or how to pass the key through any of the nine parameters. This is not enough information for an agent to invoke the tool 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?

Although the schema descriptions cover all 9 parameters, the tool description refers to a 'key' that does not appear anywhere in the schema properties (ref, url, city, feed, host, json, path, zone, query). This mismatch means the description adds no usable mapping to the actual parameters and makes it difficult to know which input should contain the Jira issue key. The high schema coverage baseline is outweighed by this conflict.

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 and resource: 'Check a Jira issue key shape.' This clearly identifies the tool's purpose and distinguishes it from sibling shape checkers such as github-repo-shape, figma-url-shape, and domain-shape. It is not a tautology of the tool name and leaves no doubt about what the tool does.

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?

The purpose implies a use case: call this tool when you need to verify a Jira issue key's shape. However, it provides no explicit alternatives, exclusions, or conditions for when to prefer this tool over other shape/validation siblings. The only secondary hint is 'Key discarded,' which is not enough to constitute clear usage guidance.

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