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

The only behavioral hint is 'Key discarded', but the key is not a schema property, and the schema's own discard notes are attached to mismatched fields. With no annotations provided, the description carries the full burden of disclosing whether the tool is read-only, what it returns, or what it discards, and it does not do so.

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, with no filler words, and the intended purpose is front-loaded. As a concise statement it is efficient, though the brevity also contributes to the missing context.

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 definition is materially incomplete for invocation. An agent needs to know which schema property receives the Jira key and what constitutes a valid shape, but the description provides neither, and the schema appears to be an unrelated grab-bag of fields. This is not enough information to call the tool correctly.

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?

All seven schema parameters have their own descriptions, so the baseline is 3. However, the tool description introduces a 'key' concept that does not correspond to any property, actively confusing parameter mapping. It adds no meaning to the actual parameters and undermines the schema descriptions by describing a parameter that does not exist.

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 says 'Check a Jira issue key shape', which at face value is a clear verb and object. However, it is misleading: the input schema contains no Jira key parameter, and its actual properties (ref, url, city, feed, host, json, path) are unrelated to that purpose. An agent cannot map the stated purpose to any available parameter, so the described functionality is not actually invocable as written.

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 on when to use this tool versus sibling shape-validation tools like domain-shape, github-repo-shape, or wiki-title-ok. It also does not mention what kind of input qualifies as a Jira key or when this tool should be preferred over alternatives, leaving selection entirely to inference.

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