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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is fully covered. The description adds two useful pieces of context beyond them: the feature must be enabled for the workspace, and results are 'bounded.' It does not say what happens when the feature is disabled (empty vs. error) or how pages behave, so the addition is real but thin.

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 short sentences, purpose first, scope boundary second – front-loaded with no filler. The second sentence is arguably tangential to a list operation but earns its place by preventing misuse for payment decisions.

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?

There is no output schema, so the description carries the burden of explaining what a 'summary' contains – and it does not mention fields, counts, or statuses. For a read-only, annotated, single-parameter list tool the risk is moderate, but an agent still cannot anticipate the shape of the response.

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?

One parameter (a nested Page with limit/offset) at 0% schema description coverage. The JSON schema does supply defaults and min/max bounds, so the agent can construct a call, and 'bounded' hints at paging. But the description adds no meaning about page size trade-offs, maximum retrievable summaries, or whether offset paging is stable.

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: 'Read bounded vendor-statement summaries.' The reader knows this is a read of saved vendor statement summaries, not a mutation. It stops short of distinguishing itself from the many sibling list_*_summaries tools (bank, handwritten, import VAT, rate confirmation), so an agent must infer the boundary itself.

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 'when enabled for this workspace' clause is a precondition, and the second sentence usefully redirects payment decisions and match confirmations to the IPP website. That gives an explicit out-of-scope boundary. However, no positive guidance about when to pick this tool over list_bank_statement_summaries or export_vendor_statement_workbook, and no exclusions among siblings.

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