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

The only behavioral disclosure is 'Key discarded', which informs that the input value is not kept. There are no annotations to provide safety or side-effect details, and the description does not state whether the tool is read-only, whether it performs network access, or what happens when a key does not match. Because the description carries the full burden without annotation support, this is a sparse transparency profile.

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, front-loading the core operation in sentence one and adding a behavioral note in sentence two. There is no redundant filler, and the most important context appears first. The concise structure is a positive point, though the brevity also contributes to the lack of completeness.

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 whose purpose is checking a Jira key shape, an agent needs to know which argument holds the key, what the return value means, and whether the check has side effects. The description provides none of these, and the input schema is generic and not tied to the purpose. Without an output schema or a clear parameter engagement, the tool is effectively unusable from this definition.

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 exposes nine parameters with generic descriptions (URL, ref, city, feed, host, json, path, zone, query), none of which is named 'key' or labeled as the identifier for the Jira key shape check. The description adds no mapping or clarification on which parameter should be passed, making it impossible for an agent to invoke the tool correctly. This is a critical semantic gap that the description does not compensate for despite the 100% schema description coverage.

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 explicitly says 'Check a Jira issue key shape', which is a specific verb ('check') plus a resource ('Jira issue key'). This differentiates it from the many sibling shape validators because it targets Jira keys. However, it does not spell out what a Jira key shape looks like (e.g., PROJECT-123), and the input schema lacks a 'key' field, so the object of the check is not tied to a concrete 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?

The description gives no guidance about when to use this tool instead of the many shape-checking siblings (domain-shape, figma-url-shape, github-repo-shape, etc.). It does not mention criteria, alternatives, or any scenario in which this is the appropriate call. An agent is left unsupervised on which tool to pick for a Jira key check.

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