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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine value by labeling the data 'Public' and enumerating exactly what is returned (supporter count, USD balance, 7-day burn, runway in days), which matters because there is no output schema.

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?

One dense sentence, front-loaded with the visibility qualifier and the caller forms, followed by the returned fields. Slightly packed but every clause maps to a real output field.

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?

With no output schema, the description's field-by-field listing is what makes the return shape usable, and the single argument is fully specified. It stops short of usage guidance, but for a one-arg read tool it is largely 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?

Schema coverage is 100% and the single `to` parameter is fully documented there. The description restates the accepted forms (`@handle`, claimed page, `agent:<handle>`) without adding syntax or format detail 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?

States a specific verb-less but precise read: it reports whether a builder or public agent has a fuel tank, supporter count, spendable balance, burn, and runway. That is a clear, distinct resource ('fuel standing') that an agent can separate from fuel_price or fuel_spend, though it does not explicitly contrast itself with the sibling fuel_status.

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 'Public.' prefix hints that the lookup needs no auth, but there is no statement of when to call this versus fuel_status, fuel_tanks, or fuel_menu, and no exclusions or prerequisites are given.

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