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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Key discarded,' which implies read-only behavior, but it does not specify which parameter is the key, nor does it mention whether any network calls occur, what happens to the other parameters, or any side effects. The parameter descriptions inconsistently mention 'discarded' for some but not all, adding confusion.

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, which is technically concise, but it is under-specified to the point of being useless. It omits critical information about how to use the tool, which parameter is the key, and what constitutes a valid shape. Conciseness should not sacrifice necessary guidance; this is not appropriate brevity but rather a placeholder.

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?

For a tool with 9 parameters, no annotations, and no output schema, the description is grossly incomplete. It does not explain how to specify the Jira key, what the expected output is (e.g., boolean, string), or any error conditions. The tool is essentially unusable without further clarification, especially given the unrelated parameter set.

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 schema coverage is 100%, the description adds no mapping between parameters and the tool's purpose. The parameters (ref, url, city, feed, host, json, path, zone, query) are diverse and none obviously correspond to a Jira key. The description fails to clarify which parameter to use, so it adds no value beyond the schema and actually leaves the purpose ambiguous.

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'), but it does not define what 'shape' means (e.g., regex, format) and none of the nine parameters appear to be a Jira key, making it unclear which parameter to use. It also fails to differentiate from sibling shape-checkers like domain-shape or github-repo-shape, which perform analogous checks.

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 alternatives. With 26 siblings including multiple shape-checking tools, the absence of any selection criteria is a major gap. The description does not mention any conditions or exclusions.

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