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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description needs less safety disclosure. It adds only generic pagination/filtering context and does not surface notable quirks such as the 'findings' include behavior, which is left to the schema. No contradiction exists.

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 description is one tight sentence with zero filler. It front-loads the core operation, then attaches the two key modifiers (pagination, filtering) without redundancy.

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 a rich input schema, annotations covering safety, and an output schema present, the description does not need to explain return values or parameter details. It gives sufficient list-operation semantics, though it could add a one-line pointer contrasting it with smi_get_deep_report for singular retrieval.

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 100%: all nine parameters have their own meaningful descriptions. The tool description adds no parameter-level detail beyond the generic phrase 'optional filtering,' so the baseline of 3 applies.

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 uses a specific verb ('Lists') and resource ('SMI deep reports'), and immediately signals the operation's scope with 'pagination and optional filtering.' This clearly separates the tool from siblings like smi_get_deep_report, smi_create_deep_report, and smi_list_exports.

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 description only implies usage through the verb 'Lists'; it does not explicitly say when to choose this tool over smi_get_deep_report or smi_list_exports. An agent can infer the basic use case but receives no guidance about exclusions or alternatives.

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