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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'No identifiers are retained' but does not clarify whether the operation is read-only, whether it requires authentication, what side effects exist, or what the output looks like. The safety profile is only partially disclosed via the 'discarded' notes in the schema, not the description itself.

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 only one sentence, which is concise, but it is under-specified rather than efficiently informative. It front-loads the main phrase but leaves out essential context. It is not verbose, but the brevity works against clarity, making it minimally acceptable.

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?

This is a 9-parameter tool with no output schema and no annotations. The description provides almost no context about what the tool does, how it processes these heterogeneous inputs, or what the classification result looks like. An agent cannot reliably invoke it correctly without additional documentation. This is critically incomplete for the tool's 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?

Schema description coverage is 100%, so the baseline is 3. The schema already documents each parameter with specifics like 'discarded after the shape check' or 'no disk access'. The description adds no additional meaning beyond the schema, so it does not exceed the baseline.

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 'Show how this request is classified' is vague—it never specifies what 'request' refers to, what 'classified' means, or what resource/operation is involved. It does not distinguish itself from sibling tools like 'validate-json' or 'domain-shape', which have clear verbs and resources. It is not a pure tautology but fails to convey a concrete 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?

There is no guidance on when to use this tool versus alternatives. The description mentions no conditions, prerequisites, or exclusions. Given the large sibling set (e.g., 'fetch-status', 'validate-json', 'normalize-url'), the absence of routing guidance leaves the agent guessing.

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