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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantial operational detail beyond them: the 31-day window limit, the fact that Qgiv has no server-side paging so a busy range is fetched whole and sliced client-side, and the underlying POST endpoint. This warns the agent about cost/latency behavior that annotations cannot express.

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?

Four dense sentences, each carrying distinct information: range semantics, paging mechanism, field parity with a sibling, and the no-server-side-paging caveat plus endpoint. Nothing is repeated and the scoping constraint is front-loaded.

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 carries return-shape burden and partially does so by pointing to qgiv_list_recent_transactions for field parity. Combined with full schema coverage and rich annotations, the agent has enough to call it correctly; the only minor gap is that the actual response envelope is only implied, not described.

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%, so the baseline is 3, and the description adds the paging model (offset/limit slicing) and that bounds are inclusive. It does not explain include_contact or any date-format nuance beyond the schema, so it is a modest improvement rather than a full one.

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 (list), resource (transactions), and scope (between two dates, inclusive, max 31 days). It also differentiates itself from siblings by noting the same field set as qgiv_list_recent_transactions and by naming the date-range constraint, distinguishing it from qgiv_list_transactions_after_id.

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?

Gives clear operational context: 31-day cap per call, and explicitly advises using a shorter range when a range is too large. It implies the alternative (qgiv_list_recent_transactions) via field parity but never states when to prefer that sibling over this one, so it stops short of full when/when-not routing.

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