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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds genuinely new behavioral context: no authentication is required, and because there is no output schema it usefully describes the returned record fields. It stops short of noting ordering guarantees or whether totals are cached/live.

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?

Front-loaded with the return payload and scoped tightly to three sentences. The trailing 'Args: { limit?: ... }' sentence largely duplicates the schema, so it doesn't fully earn its place, but the whole block is compact with no filler.

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 no output schema, the description covers everything an agent needs: what is returned, that no auth is required, and the limit semantics. Nothing material 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 description coverage is 100% and the single limit parameter's range and default are already fully documented in the schema. The description restates '1-50, default 10' without adding syntax, ordering meaning, or behavior beyond what the schema provides, so the baseline 3 applies.

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?

Specific verb and resource: it returns the running USD total, donor count, and most recent settled donations shown on the public donor wall. The return payload is enumerated (name, amount, message, tx, ts), so an agent knows exactly what it gets and can distinguish it from the write-side sibling ic_donate.

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 phrase 'shown on the public donor wall at /donate' and 'No auth required' imply the read-only public scenario, but the description never states when to prefer this over ic_donate or any other sibling, nor any exclusions. Usage is inferable but not spelled out.

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