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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses that the call is free and unauthenticated, that agent names resolve to wallet addresses, that a wallet with no grant reports status 'none', and what specific values will be returned.

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 front-loaded with the core purpose and returns, followed by use context and parameter semantics. Every sentence adds value, though there is minor duplication between the '[FREE]' prefix and the closing 'Free, unauthenticated.'

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 single-parameter read tool with an output schema, the description fully equips an agent to call it correctly: what it returns, how the parameter works, the 'none' status semantics, and when to use it. Nothing essential is missing.

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 coverage for the single parameter is 0%, so the description must compensate and it does. It explains that agent_wallet accepts either a 0x address or an AgentWorld agent name, and that known names are resolved to their wallet—meaningful guidance the schema does not provide.

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 opens with a specific verb and resource: 'Read the spend authority on any agent wallet: who it spends for, and under what bounds.' It clearly differentiates from the sibling publishing and revocation tools by framing this as a read operation on an agent wallet's spend envelope.

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 gives explicit usage context: a counterparty uses this before extending credit, accepting a purchase commitment, or delegating paid work. It explains the behavioral rationale for that usage, though it does not name alternatives or describe when not to use this tool.

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