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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds context about the content (third-party URLs and CLI commands) without contradicting annotations. It does not describe output format, but for a simple link-retrieval tool with annotations, this is adequate.

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 two sentences, front-loaded with the main purpose, and includes no unnecessary details. Every sentence adds value: the first states what URLs are provided, the second adds verification guidance and CLI commands.

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 simplicity (no parameters, no output schema), the description covers essentials: the specific validator, the list of platforms, and the inclusion of CLI commands. It could mention how to interpret the links or any external dependencies, but the openWorldHint annotation covers the external nature. Overall, it is sufficiently complete.

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 tool has zero parameters, so the baseline is 4. The description does not need to explain parameter semantics, and no schema details are required. The description's focus on output content 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 clearly states the tool's function: retrieving third-party verification URLs for the Blueprint validator, listing specific platforms. It distinguishes itself from sibling tools like verify_transaction or check_address_type by focusing on URL retrieval rather than direct verification actions.

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 provides clear context: this tool is for obtaining verification links and includes CLI commands for on-chain verification. The phrase 'Verify every claim independently' implies a usage context, though it does not explicitly name alternatives or exclusions. This is clear guidance, but not as explicit as naming a specific alternative tool.

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