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

The only behavioral disclosure is 'Key discarded', implying the input is not persisted. However, with no annotations provided, the description should explain what the tool returns (e.g., boolean, error message) and whether it makes any network calls or has side effects. This is insufficient for an agent to trust the tool.

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 a single sentence, so it is concise, but it lacks essential structure such as a clear statement of the expected input format or output. It is under-specified rather than efficiently front-loaded; the one sentence does not earn its place by conveying critical information.

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 9 optional parameters, no output schema, no annotations, and a one-line description, the tool is critically incomplete. An agent cannot determine what to pass, what to expect back, or when to invoke it. The description fails to compensate for the absence of structured metadata.

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?

Although the schema documents all 9 parameters (100% coverage), the description does not connect any of them to the Jira key concept. Parameters like 'city' and 'feed' appear unrelated to Jira keys, and there is no hint which parameter holds the key to check. The description adds no semantic value beyond the schema, and the mismatch between tool name and parameters creates confusion.

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 resource ('Jira issue key shape') and a verb ('Check'), but it doesn't define what a valid Jira key looks like (e.g., PROJECT-123) or how it differs from sibling shape tools like 'github-repo-shape' or 'domain-shape'. The term 'shape' is vague, and the tool's name is not enough to convey the exact format expected.

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?

There is zero guidance on when to use this tool versus alternatives. No context about Jira key validation, no mention of when not to use it, and no reference to sibling tools. An agent would have no idea which scenario calls for this tool.

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