green-router__verify_green_certificate

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

No annotations provided. Description mentions recomputing and comparing but does not disclose side effects, permissions, or rate limits. Incomplete for a no-annotation 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 relatively concise but includes promotional text ('FREE forever (GR5):') that is unnecessary and slightly distracts from the core action.

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?

Lacks details on the tool's output or return format; only mentions surfacing a purchase_id. Missing information about success/error indicators or full response, making it incomplete for a verification tool with no output schema.

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 single parameter certificate_id has no schema description (0% coverage) and the description does not explain its format or origin, adding no value beyond 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 clearly states the tool recompares a certificate's footprint against certified numbers and surfaces a purchase_id, differentiating it from sibling tools like green-router__list_green_certificates and offsets__verify_certificate.

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 explicit when-to-use guidance or differentiation from the many verification sibling tools (e.g., provenance__verify_certificate, offsets__verify_retirement). Only implies a follow-up step to verify retirement.

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