list_aws_savings_plans

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful behavior beyond them: it documents the pageToken pagination loop and the stop condition. It also clarifies that omitting filters returns all Savings Plans. The marketing first sentence is misleading, but the operational description does not contradict the annotations.

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 pagination and filter guidance are concise and well placed after the first sentence. The opening sentence is promotional fluff that suggests planning and automation capabilities this read-only list endpoint does not actually provide, so not every sentence earns its place.

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?

The description fully covers pagination and main filters, which are common invocation pitfalls. However, it omits maxResults behavior, tenant/header handling, and any explicit guidance on how Savings Plans listing relates to the many AWS commitment siblings, so the agent still lacks some selection and invocation context.

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?

With schema description coverage at only 14%, the description carries real weight. It explains type and status filters and pageToken, but it does not cover maxResults, X-Tenant-Id, or managementAccountId beyond the phrase 'AWS organization.' This is partial compensation for a low-coverage schema.

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 core operation is clear: 'Returns a paginated list of Savings Plans for the specified AWS organization,' naming a specific verb, resource, and scope. However, the opening marketing sentence about evaluating commitments and automating purchases muddies the immediate purpose, and it doesn't explicitly differentiate from close siblings like list_aws_reserved_instances.

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 gives useful filter guidance ('Omit both filters to return all plans') and clear pagination instructions. It does not, however, say when to prefer this tool over alternatives such as list_aws_reserved_instances, list_aws_planned_purchases, or list_aws_recommendations, leaving selection context implicit.

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