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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only hints that values are discarded, but does not explain what is returned, whether errors are raised for invalid inputs, or whether the operation has any side effects. This is far from sufficient for a 9-parameter tool.

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 to the point of being cryptic rather than helpful. It is not well structured as an actionable statement and omits essential information, making it under-specified rather than appropriately concise.

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 nine optional parameters, no annotations, no output schema, and a highly specialized set of sibling tools, the description is completely inadequate. It does not explain how the tool behaves, what it returns, or how the parameters interact, leaving the agent unable to call it correctly.

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 input schema has 100% description coverage, with each of the nine parameters documented individually. The description adds only a general note that values are discarded, so the schema already does the heavy lifting; the baseline score of 3 is appropriate.

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 names 'tag: URI shape' but provides no clear verb, leaving ambiguous whether the tool validates, normalizes, or merely tags the input. It does not distinguish itself from sibling shape-checking tools like domain-shape or file-path-ok, and the phrase 'value discarded' is too vague to clarify the core action.

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. With many sibling validators and formatters, the description provides no context, prerequisites, or routing information.

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