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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds real content context the annotations cannot: results are summary-only with per-transaction rows deliberately omitted, which tells the agent not to expect line-item detail.

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?

A single front-loaded sentence that states the resource ('latest statement(s)'), the output shape ('summary totals'), the key exclusion ('per-transaction rows left out'), and the endpoint. No filler or restatement of the title.

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 must carry return-value meaning, and it only partly does — it says summary totals without describing what a statement record contains. More importantly, it says the target is 'the organization or form' yet the schema has no parameters, so how the scope is selected (auth context? default?) is left unexplained. Adequate but with a clear gap.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry — the baseline for a 0-param tool is 4. Nothing is missing on this dimension.

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?

Specific verb+resource: retrieves the 'latest statement(s)' with 'summary totals' and explicitly notes per-transaction rows are excluded, so the agent knows exactly what it gets. However, it never distinguishes itself from siblings like qgiv_get_statement (singular) or qgiv_list_statements, leaving the 'why this one' question open.

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 word 'latest' implies a recency-based retrieval distinct from list_statements, which suggests when an agent would reach for this tool. But there is no explicit when-to-use, no exclusion, and no pointer to any alternative sibling — usage is inferred rather than stated.

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