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

readOnlyHint=true already establishes the read-only profile, so the bar is lower. The 'Bloomerang: GET /appeals' line reinforces a safe read but adds little beyond the annotation; pagination behavior, result shape, and default ordering are left to the 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?

Single front-loaded sentence with a concrete parenthetical example, followed by a short API pointer. No waste, though the 'Bloomerang: GET /appeals' tail is marginally redundant with the readOnly annotation.

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 6-param filtered list tool with no output schema, the description characterizes the resource adequately but says nothing about return contents or the practical effect of skip/take/search. Minimum viable, with clear gaps.

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%, so ids/skip/take/search/is_active/last_modified are already documented in the schema. The description adds no parameter syntax or filtering guidance, so 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?

Clear verb+resource ('List appeals') with a domain gloss that explains what an appeal is ('the specific asks... that gifts are attributed to'). This differentiates it from generic list tools, though it never names how it differs from siblings like list_campaigns or list_funds.

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?

No when-to-use guidance, no alternatives named, no mention of when to reach for list_appeals versus list_campaigns/list_funds or the search endpoint. The agent must infer usage entirely from the resource name.

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