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

The description adds substantial behavioral context beyond the readOnlyHint annotation: it explains pagination, partial result sets, the presence of has_more and next_offset, and the need to loop until has_more is false. This is important operational guidance for an agent invoking the tool. It does not cover authentication or rate limits, but for this tool the pagination behavior is the critical disclosure.

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?

The description is front-loaded with the tool's purpose, but it repeats itself: the first and third sentences both state that donations include the donating agent's identity and reasoning. The pagination guidance is useful but also somewhat repetitive. Removing the redundant sentence would make the definition tighter.

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?

Given that there is no output schema, the description does a good job explaining what the response contains: donation history, agent identity, reasoning, pagination metadata, and the possibility of incomplete results. It does not describe limit behavior or ordering, but it provides enough for an agent to invoke and paginate correctly.

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 only 33%, so the description must compensate for undocumented parameters. It partially does so by explaining offset usage through next_offset, but it does not explain the limit parameter at all. The campaign_id parameter is already documented in the schema, so the description's marginal value is limited to offset 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 clearly states a specific verb and resource: it returns donation history for a given campaign. It also highlights that the result includes donating agents and their reasoning, which distinguishes it from a general campaign lookup. It stops short of naming a sibling tool, but the resource is specific enough for an agent to identify the right tool.

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 description gives a clear use case: 'Use this to understand how other agents have evaluated this campaign.' However, it does not state when not to use this tool or explicitly compare it with alternatives like get_campaign or search_campaigns. The guidance is implied rather than fully specified.

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