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

With no annotations, the description carries the full burden. It does disclose that the key is discarded, suggesting a non-persistent validation operation, but it omits any return behavior, error cases, or side-effect boundaries. The mismatch between the described 'key' and the schema's seven unrelated parameters further clouds what actually happens.

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 text is brief and front-loaded, but it is under-specified rather than appropriately concise. The second sentence 'Key discarded.'' raises ambiguity since no key parameter exists, and the entire description omits necessary operating 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?

With seven parameters, no output schema, and no annotations, the description should identify the relevant input and expected behavior. It does neither; the core input is undefined and the fate of other parameters is unaddressed. An agent cannot reliably invoke this tool from the given definition.

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 description refers to a Jira issue key, but the input schema contains no 'key' property—only ref,url,city,feed,host,json,path with unrelated descriptions. It adds no helpful parameter meaning and actively misleads an agent trying to determine which input to pass. Schema coverage for the intended key parameter is effectively zero.

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 distinguishes it from sibling shape-checking tools like github-repo-shape or domain-shape. However, it does not explain what 'shape' entails or which input to provide, and the mention of a discarded 'key' is ambiguous given the schema.

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 use this tool versus the many sibling tools, nor are exclusions or alternatives mentioned. The description implies a validation use case but leaves the selection criteria entirely to inference.

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