decode_lease_uri

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

Discloses it is offline and verified against canonical implementation, implying safety and determinism. No annotations exist, so description carries the burden well. Could mention error handling but reasonable.

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?

Three concise sentences cover purpose, inputs, and verification. No wasted words.

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?

Describes inputs and outputs adequately given single parameter and no output schema. Could specify return structure (object vs list) but fields are listed.

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 already describes parameter fully (100% coverage). Description adds no new parameter-level meaning beyond restating acceptable formats.

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 decodes an Evernode lease URIToken URI and lists the exact output fields (lease index, amount, etc.), distinguishing it from siblings like decode_uritoken_id.

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?

Explicitly mentions acceptable input formats (hex, base64, raw buffer) and that it operates offline. No explicit contrast with alternatives, but the specificity makes usage clear.

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