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

Annotations only indicate it's not read-only, but the description adds critical context: it reveals the tool does not directly transfer funds but returns payment instructions (amount + address), and that crediting happens after confirmation. This exceeds what annotations provide.

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?

Two sentences, front-loaded with the core purpose, and every phrase earns its place. No fluff, yet it covers purpose, return value, and process.

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 tool with no output schema, the description explains the return value and the confirmation flow. It doesn't mention prerequisites (e.g., having an active tab), but that's a minor gap given the simplicity.

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 is 100% and the schema already describes the 'doge' parameter as the amount to add. The description adds minor context ('returns an EXACT DOGE amount') but doesn't clarify if the returned amount differs from input (e.g., fees). Baseline 3 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?

States a specific verb 'top up' and resource 'tab', and clarifies the unique behavior of returning an exact DOGE amount and house address. Distinguishes itself from siblings like 'tab' (balance check) and 'tip' (gratuity) by explicitly focusing on funding the tab.

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?

Implies usage context ('top up your tab') but does not explicitly mention alternatives or when not to use it. No exclusionary guidance, though the sibling list makes the distinction somewhat obvious. Adequate but not explicit.

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