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

With no annotations, the description carries the full burden, but the only behavioral disclosure is 'Key discarded.' It does not state whether the operation is read-only, what it returns, or what validation rules define a valid Jira issue key. The discard note is useful but insufficient for safe tool invocation.

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 with the primary action front-loaded. There is no filler or redundancy; every word earns its place, even though the content is incomplete elsewhere.

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 missing essential context: which parameter is the key, what the expected Jira key format is, what the return value means, and whether any input is required. With no annotations and no output schema, the description leaves an agent unable to call the tool correctly or interpret its result.

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 tool-level description never identifies which of the nine schema parameters should hold the Jira issue key, and the parameter descriptions are unrelated ('url', 'city', 'feed', 'json', 'query', etc.). Although schema coverage is 100%, the descriptions actively mislead an agent about how to call this tool. This is a fundamental parameter-semantics failure.

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.' This clearly distinguishes the tool from sibling shape-checkers like domain-shape and github-repo-shape. The 'Key discarded' fragment is odd but does not obscure the core purpose.

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 given about when to prefer this tool over alternatives or what kinds of refs/keys are appropriate. There is no mention of exclusions, prerequisites, or comparison to sibling shape-validation tools. The agent must infer usage from the name alone.

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