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

The only behavioral disclosure is 'Key discarded,' which is useful given the absence of annotations. Still, the description does not reveal what the tool returns for valid vs invalid shapes, whether errors are thrown, or whether any external/network activity occurs.

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 compact, front-loaded with the main action, and contains no filler. The terse style costs it only because the missing parameter mapping and return-behavior information are required for correct invocation.

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?

Given nine optional parameters, no output schema, and no annotations, the description is not complete enough for an agent to invoke the tool correctly. It lacks the valid key format, the parameter to use, and any statement about the response on success or failure.

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?

Even though schema coverage is 100%, the description fails to connect the concept of a 'Jira issue key' to any of the nine schema properties. None of the parameter names is 'key,' so without an explicit mapping the agent cannot tell whether to pass ref, query, url, or some other field.

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 clearly states a specific action and resource: check a Jira issue key shape. This distinguishes it from sibling shape tools such as github-repo-shape and domain-shape. However, it never identifies which input parameter carries the key, so the purpose is clear but the invocation mapping is not.

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 phrasing implies the tool should be used when a Jira issue key shape needs to be validated, but there is no explicit when-to-use or when-not-to-use guidance. It also does not mention alternatives or selection criteria among the many sibling validation utilities.

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