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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds real value by explaining what the number actually aggregates (bot burns and all earlier burns) rather than just naming it. It stops short of stating the return shape or freshness/update cadence, which keeps it off a 5.

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 definition before the routing hint, with no filler or restatement of the tool name. Every clause carries either definitional or disambiguating information.

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 zero-parameter read-only metric with no output schema, the description supplies everything an agent needs: what is measured, how it is defined, and when to prefer the sibling. The absence of an output schema is offset by the description naming the return value as a total.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims are made or needed.

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 metric (total $BOBAI permanently burned) and pins down its definition — the balance held by the dead/zero address, composed of the buyback-and-burn bot's burns plus prior ones. It also explicitly separates itself from bobai_token_info, so an agent can choose between them without opening either schema.

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?

Gives both the selecting condition ('use it when only the burned total is needed') and the named alternative ('bobai_token_info returns it with the other supply figures'). That is an explicit when-to-use plus a when-to-use-the-other, leaving nothing to inference.

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