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

With no annotations, the description carries the behavioral disclosure burden. It adds one useful privacy trait, 'No identifiers are retained,' and the schema descriptions reinforce 'discarded' for several fields. However, it does not disclose the return format, whether any external calls occur, or any other side effects, so behavioral transparency is only partial.

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 concise and front-loaded with the core action. It is also overly terse for a tool with nine parameters and many siblings, and the privacy sentence is policy rather than actionable usage guidance.

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?

The description is inadequate for a tool with nine optional parameters, no output schema, and no annotation support. It does not explain how the classification is returned, how to choose the right parameter, or how this tool relates to the 27 sibling tools. An agent cannot reliably select and invoke it based on the description alone.

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 coverage is 100%, and each parameter already has a descriptive comment such as 'Git ref name; discarded after the shape check.' The tool description adds no parameter-specific meaning, so it meets the baseline but does not enhance 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 description says 'Show how this request is classified,' which names an action and an object, but it never defines what classifications exist, what inputs drive them, or how this differs from sibling tools like browser-url-ok or validate-json. The purpose remains vague and does not distinguish the tool from its many alternatives.

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 compatibility instead of the sibling-specific tools. The description does not explain which parameter to supply, what request shapes are supported, or when a direct check like normalize-url or validate-json would be more appropriate. Usage must be inferred entirely from the schema and tool name.

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