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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the description's 'Read-only' is redundant. The description adds context about the data type (cost-intelligence) but no additional behavioral traits such as pagination behavior, default ordering, or potential rate limits. Given the annotations cover safety, the description adds minimal value beyond them.

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 a single sentence that front-loads the purpose, resource, and key capabilities. There is no fluff, and every phrase earns its place by clarifying what the tool does and its main options.

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 list tool with a nested filter object and an output schema, the description provides the high-level purpose but omits details like the required companyId, pagination token semantics, and allowed status enum values. Since the schema is available, an agent can infer these, but the description alone is not fully self-sufficient. It is adequate for orientation but not complete for correct invocation without schema inspection.

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 compensate by explaining parameters. It mentions 'status/type filtering' but does not map to filter.types and filter.statuses, nor explain companyId, pageSize, or pageToken. It fails to indicate that companyId is required and does not describe the value formats. This is insufficient for a tool with zero schema-level descriptions.

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 clearly states the verb 'List' and the resource 'cost-intelligence insights', defines what those insights are (savings opportunities, spend anomalies), and notes key features (status/type filtering and pagination). This distinguishes it from siblings like insight_get_insight (singular) and insight_get_savings_summary (summary), so an agent can tell it apart.

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 implies the tool is for listing insights but does not explicitly state when to use it versus alternatives like insight_get_insight or insight_get_savings_summary. There is no mention of when not to use it or which sibling handles a single insight. The usage context is inferred but not spelled out.

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