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

No annotations are provided, so the description carries full burden. "Value discarded" hints at a stateless shape check, which is useful, but it says nothing about whether this is read-only, whether it throws on invalid input, what the response shape is, or which of the nine inputs actually get used for the DID-shape check. The omission is significant for a nine-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?

It is short, but it is not front-loaded with a verb or outcome; the reader has to infer what the tool does from a noun phrase. Brevity here reflects under-specification rather than efficient conciseness.

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?

Nine parameters, no annotations, no output schema, and a description that does not explain which parameters trigger which check, what the return value is, or which of the nine inputs actually matter. The definition is far too thin for the surface area it exposes.

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 schema already documents all nine parameters, and each one's role is clear from the schema text alone. The description itself adds no parameter meaning. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

"DID method shape, value discarded" does not state a verb or an outcome. It reads as a label rather than a description of what the tool does; an agent cannot tell what "shape" means or what the call returns. Sibling names like domain-shape and github-repo-shape suggest a family, but this tool's own purpose is not articulated.

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 when-to-use, no when-not-to-use, no mention of any alternative. The sibling set contains multiple overlapping shape/validation tools (file-path-ok, validate-json, browser-url-ok) and the description gives no routing guidance at all.

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