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

No annotations are provided, so the description carries the full behavioral disclosure burden. It discloses that the key is discarded, which is useful for privacy, but it does not state what the tool returns, whether the check is local, or any error behavior. This is only partial transparency.

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, front-loads the action, and includes a useful privacy note without filler. It is concise, though the brevity leaves critical invocation details unstated.

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?

With nine optional parameters, no annotations, and no output schema, the description is far too sparse to support correct use. It does not explain which parameter holds the Jira key, what a valid shape is, or what result the agent should expect. An agent cannot reliably invoke this tool correctly from the definition alone.

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 coverage is 100%, so each of the nine string parameters has a description, giving a baseline of 3. However, none of the parameters—ref, url, city, feed, host, json, path, zone, query—obviously represents a Jira issue key, and the description does not map the key to any field. An agent cannot determine which parameter to populate for the stated purpose.

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 and resource: checking the shape of a Jira issue key, and adds a privacy-relevant note that the key is discarded. This makes the core function clear, though it does not explicitly differentiate itself from sibling shape-checkers like github-repo-shape or domain-shape.

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 only usage cue is the purpose statement itself; an agent can infer the tool is for validating whether something is a Jira issue key. However, there is no explicit guidance about when not to use it, what counts as a valid key shape, or which alternative validation tool to choose among the many siblings.

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