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

With no annotations, the description must fully carry the behavioral disclosure. It only states that identifiers are not retained, which gives a privacy guarantee but does not disclose whether the operation is read-only, what it does with the inputs, or what output to expect. This is insufficient for a tool with 9 parameters.

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, which is concise in length, but it is under-specified and lacks any meaningful structure. It is more akin to a placeholder than a concise description.

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 the tool's 9 parameters, zero annotations, and lack of output schema, this description is severely incomplete. An agent cannot determine what this tool does, how to invoke it, or what results to expect, making it disastrous for agent use.

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 schema provides a 100% description coverage for all 9 parameters, including per-parameter explanations. The description adds no extra semantic information, so baseline 3 is applied.

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 'Show how this request is classified,' which is vague and does not specify the nature of the classification or what inputs it applies to. It does not distinguish the tool from its siblings like domain-shape or validate-json, and the term 'request' is undefined.

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 other tools. No context, conditions, or alternatives are mentioned, leaving the agent without direction.

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