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

With no annotations, the description carries the full burden of disclosing side effects, permissions, and limitations. It only states 'Key discarded,' which is trivial and does not address the tool's actual behavior with the 9 parameters. The description does not disclose what happens to inputs, whether network/disk access occurs, or any error conditions. It is also inconsistent with the schema, suggesting the description may be for a different tool.

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 extremely short (one sentence), which would be acceptable for a simple tool, but with 9 parameters and no other context, it is under-specified. It does not front-load key information about parameter selection or behavior. The brevity is not elegant conciseness; it is inadequate.

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?

Given the tool has 9 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the return value, which parameters are relevant to the Jira key check, what 'shape' validation entails, or how the other parameters (city, feed, host, etc.) fit in. An agent cannot correctly invoke this tool based on the provided description.

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 each parameter has a description. However, the tool description does not map any parameter to the 'Jira key' concept; it adds no semantic linkage. The parameter descriptions themselves are generic (e.g., 'City name for a public weather hint') and seem unrelated to the stated purpose. The description fails to clarify which parameter (if any) is the Jira key or how the parameters are used in the check.

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 a Jira issue key shape'), but the input schema contains 9 parameters (ref, url, city, feed, host, json, path, zone, query) with no obvious mapping to a Jira key. This mismatch makes the actual purpose unclear and potentially misleading. It is not a tautology, but the resource (Jira key) is not reflected in any parameter.

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 provided on when to use this tool versus its many siblings (e.g., domain-shape, github-repo-shape, validate-json). There is no mention of conditions, exclusions, or alternatives. An agent has no basis to decide when this tool is appropriate.

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