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

No annotations are present. The only behavioral hint is 'No identifiers are retained,' which addresses data retention but not side effects, errors, or potential state changes. The tool's actual behavior (e.g., whether it performs network calls, reads files, or returns a classification based on heuristics) is not disclosed.

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 extremely short, but brevity is not a virtue here because it omits essential information. It is not front-loaded with the key insight an agent needs, and every word is wasted on a vague overview rather than concrete details.

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 heterogeneous parameters, no output schema, and no explanation of the classification logic, the description lacks critical context. An agent would have no way to predict the tool's response or decide whether this tool is appropriate for a given task. The description is grossly insufficient for the tool's apparent complexity.

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?

While the input schema covers all 9 parameters individually, the descriptions are generic and do not explain how each parameter contributes to the classification. Phrases like 'discarded after the shape check' hint at validation but leave the relationship between parameters and the output completely unclear. The description adds negligible meaning beyond the schema.

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 verb 'Show' is weak and ambiguous. It does not state what classification means, what categories exist, or how the output is structured. With 9 disparate parameters (ref, url, city, feed, host, json, path, zone, query) and a generic description, an agent cannot infer the tool's specific 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 provided on when to use this tool versus its 25 siblings. The description does not mention distinguishing scenarios, prerequisites, or conditions that would suggest calling this tool instead of a more specific one like validate-json, timezone, or weather-hint.

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