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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds that access depends on an existing workspace feature gate and that it does not file a return, which is useful context, but it does not explain gate-failure behavior or what "bounded" means in practice.

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 definition is two short sentences and front-loads the read operation before the boundary statement. It is efficient, though the feature-gate wording is vague rather than informative.

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 should clarify what these summaries contain and how pagination behaves, but it does neither. It also leaves the feature-gate dependency and sibling differentiation unexplained, so an agent lacks enough context to invoke it confidently.

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%, and the only parameter is an input object containing limit and offset. The description's word "bounded" hints at pagination but does not explain those fields, their limits, or defaults, so it does not compensate for the schema gap.

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 states a read action on "report summaries" and adds the boundary "Does not file a return," but it never says these are import-VAT summaries and does not differentiate from the many sibling list_*_summaries tools. The purpose is recognizable but too generic for confident selection.

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?

It gives no guidance on when to use this tool versus alternatives such as list_bank_statement_summaries, list_handwritten_summaries, or other report-summary tools. The feature-gate mention is a constraint, not a usage selection rule.

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