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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds the backend mapping (GET /api/v1/appeals), confirming a read operation and no contradiction. It says nothing about pagination behavior or result volume, which would have added real value beyond the annotations.

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 compact sentences plus the endpoint reference; the resource definition is front-loaded and nothing is redundant. Slightly dense in the field listing, but no wasted text.

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-required-parameter read-only list endpoint with no output schema, the description covers the entity, its attributes and the endpoint. Missing only return-format/pagination shape, which for a simple list tool is a minor gap.

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 both limit and offset carry full descriptions including defaults and next_item guidance, so the schema does the heavy lifting and a baseline 3 applies. The description adds no pagination syntax or semantics of its own.

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 title supplies the verb ('List') and the description defines the resource richly — fundraising appeals are mailings, emails and asks, with campaign, date, goal, cost and active flag. It does not, however, distinguish itself from siblings like lgl_list_campaigns or lgl_list_funds, which an agent could confuse since 'campaign' appears as a property here.

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 sentence 'Use the ids and names when recording gifts or filtering searches' gives downstream usage context, implying the results feed lgl_create_gift and search filters. It stops short of stating when to call this versus lgl_list_campaigns or other list endpoints, so usage is only implied.

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