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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds the endpoint (GET /search/orders) and default sort direction, but says nothing about pagination behavior, rate limits, or result-size expectations for a full listing.

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 no filler: scope and returned fields first, filters and endpoint second. Every clause carries information an agent would otherwise have to infer.

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 usefully enumerates the returned fields, which is what an agent needs. It stops short of explaining paging (cursor via starting_after, limit 1-50) or ordering details beyond 'newest or oldest first', leaving a small gap for a 12-parameter list tool.

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 all 12 parameters are already documented in the schema. The description's filter list mirrors those parameters without adding format, syntax, or precedence details, which is the correct baseline 3 when the schema carries the load.

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 donation orders'), disambiguates the record grain ('one per checkout'), and enumerates the payload fields returned (order number, billing name/address, form, total, currency, status). An agent can tell this apart from givingfuel_get_order and givingfuel_list_transactions without opening a 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 clause 'Filter by form, status, donor email, customer id, order number or dates' implies when the tool is useful, but there is no explicit guidance on when not to use it or which sibling to pick instead (e.g., get_order for a single known order). Usage is inferable rather than stated.

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