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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the notable fact that reads go through POST /pledges/list, which is useful behavioral context, but discloses nothing about pagination limits or result shape.

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 dense sentences with zero filler; the disambiguation from pledge records is front-loaded and the endpoint is noted compactly at the end. Nothing could be removed without losing signal.

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?

There is no output schema, and the description compensates by listing the fields returned, which is exactly what an agent needs here. It is slightly thin on whether results are scoped to one form or all forms, which matters for a form-configuration listing endpoint.

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 both parameters (limit, offset) are fully documented in the schema, so the description need not carry parameter meaning. The field list it gives (title, value, frequency, etc.) describes return content rather than parameters, so it adds little to parameter semantics.

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 description names a specific resource (pledge options configured on form(s)), enumerates the configured fields, and explicitly distinguishes it from donor pledge records, which is the closest sibling (qgiv_get_pledge). An agent can tell what it returns without opening the 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?

The negative clause 'not donors' pledge records' excludes the adjacent use case and implicitly routes to qgiv_get_pledge, but no alternative is named explicitly and no when-to-use condition (e.g., setting up a form vs. reconciling donations) is given. Usage is implied rather than stated.

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