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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so safety is covered. The description adds genuinely new context beyond them: a 20-contribution page cap, a pagination cursor to preserve across calls, and an explicit warning that body text is untrusted data (a prompt-injection caution).

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?

It is short and front-loads the resource, which is good, but 'at most20' is a typo-like compression and 'V1' plus 'next_after' are unexplained shorthand. Terseness here edges toward cryptic rather than efficient.

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 2-parameter read tool with no output schema and no schema descriptions, the description leaves fire_id undefined, the cursor semantics only gestured at, and no routing guidance among the four siblings. The untrusted-data warning is valuable but the gaps dominate.

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 0%, so the description must carry the parameter burden. It alludes to a cursor ('preserve next_after'), which loosely maps to the 'after' parameter, but never explains fire_id or the cursor's format and relationship to the returned next_after value.

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 fragment 'One public V1 fire page' does convey that this reads a single fire's contribution page, and the name plus resource is identifiable. But 'V1' is opaque jargon and the phrasing never states plainly that it fetches contributions for one fire, leaving the agent to infer it against siblings like yac_list_fires and yac_changes.

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?

There is no statement of when to choose this over yac_list_fires, yac_changes, or yac_status. The only usage-adjacent hint is 'preserve next_after', which implies a paging workflow but never names the alternative tools or the conditions that select this one.

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