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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds two genuine traits: results are 'bounded' (paginated, matching the limit/offset with maximums) and rates are redacted unless the caller holds load-financial permission. That permission-dependent redaction is exactly the kind of non-obvious behavior worth disclosing.

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 with two clauses, each earning its place: what is read and the permission caveat. Nothing is padded or redundant.

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?

For a one-parameter list tool with no output schema, the description covers purpose and the key permission behavior, but says nothing about what a 'summary' contains, ordering, or what is returned when the caller does have load-financial permission. Adequate, with clear remaining gaps.

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 0%, so the description must carry weight; 'bounded' signals pagination but never explains limit/offset semantics, defaults, or the maximums. The schema itself constrains both fields with defaults and min/max, which keeps this at a viable 3 rather than lower.

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-plus-resource: 'Read bounded saved load-confirmation summaries' tells the agent exactly what entity is returned and that results are paginated. It does not, however, explicitly separate itself from the many sibling list_*_summaries tools (handwritten, bank statement, import VAT, vendor statement); the reader must infer differentiation from the resource name alone.

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?

No when-to-use, when-not, or alternative routing is given. The only conditional in the sentence concerns permission-based data hiding, not invocation guidance, so the agent gets no help choosing between this and search_documents, list_loads, or sibling summary listers.

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