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

Annotations already declare readOnly/idempotent/no-destructive, so the safety profile is covered. The description adds real context beyond that: the exact return fields, the inclusion of a 12-month forecast, and the offset-style paging behavior, which the agent would otherwise not know.

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?

Dense but efficient: purpose, fields, filter, paging all front-loaded in a few clauses. The trailing endpoint hint ('POST /reporting/recurring/...') is the one element that may not earn its place for an agent, but it does not bloat the definition.

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?

With no output schema, the description compensates by enumerating the returned fields and the forecast, and it covers filtering and pagination. An agent has enough to call it correctly, though it lacks any note on result ordering or large-result limits beyond the schema caps.

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 limit, offset, status and include_contact are already documented. The description only restates status filtering and offset/limit paging, adding no syntax or meaning beyond the schema. Baseline 3 for full schema coverage is appropriate.

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?

States a specific verb and resource ('list recurring donation schedules') and enumerates the fields returned (id, dates, frequency, amount, state, donor, forecast). This clearly distinguishes it from the singular qgiv_get_recurring_schedule and from list_pledges.

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?

It notes the status filter options and that paging uses offset/limit, which implies when the tool is useful (browsing schedules by state). However, it never names an alternative or states when to prefer this over qgiv_get_recurring_schedule or list_pledges, 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.