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

The description adds value by confirming the 'read-only' nature of the operation through words like 'Classifies' and 'checks existence.' Since annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), the description fulfills its role with a baseline level of additional context.

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, efficient sentence that packs all necessary information—input types and core functionality—without any unnecessary verbiage.

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?

For a tool dealing with diverse identifier formats, the description is highly complete. It tells the agent exactly what input types are acceptable for classification and existence checking.

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?

With 0% schema description coverage, the description is vital. It defines the semantics of the `identifier` parameter by specifying that it can accept four distinct types of inputs (address, transaction hash, block number, or 4-byte selector), which is critical for the agent.

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 clearly states the purpose: classifying and checking the existence of an identifier. By listing specific types (address, hash, block number, 4-byte selector), it provides a necessary functional definition for the tool.

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?

The description does not explain when to use this tool versus others in the ecosystem. Since many sibling tools also operate on addresses or selectors, the description lacks guidance on whether this should be a pre-check for a more specialized call.

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