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

With no annotations provided, the description carries the full burden for behavioral disclosure. 'Key discarded' adds a small hint that the input is not retained, but the description does not explain return values, whether the check returns a boolean or throws, what constitutes a valid shape, or any side effects. This is insufficient for a validation tool without an output schema.

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 core purpose in the first sentence. The second sentence attempts to add a behavioral note. It is concise with no fluff, though 'Key discarded' is cryptic and could have been clearer.

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 9 optional parameters, no required parameters, no output schema, and no annotations. The description does not explain how to supply the Jira key, what the check returns, or what shape is considered valid. Given the complexity and the mismatch between the description and schema, this is critically incomplete.

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 has 100% description coverage, but its nine properties (ref, url, city, feed, host, json, path, zone, query) are unrelated to a Jira issue key, and there is no 'key' parameter at all. The tool description does not clarify which parameter should receive the Jira key, making it impossible to invoke correctly based on the given information. The high schema coverage does not rescue this mismatch.

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 names a specific verb ('check'), a specific resource ('Jira issue key shape'), and implies a validation function. It also distinguishes this tool from sibling shape-checkers like github-repo-shape and domain-shape. However, it does not explicitly contrast it with those siblings, so it stops short of a 5.

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 description provides no guidance about when to use this tool versus alternatives. It does not mention when not to use it, such as for URLs, GitHub repos, domains, or other non-Jira inputs. The sibling tool names imply a broader shape-checking family, but the description itself leaves usage inference entirely to the agent.

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