list_aws_savings_plans

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so the description's value is in disclosing pagination behavior: call again with the returned pageToken, and stop when pageToken is absent. This is useful behavioral context beyond the schema and 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 core sentences are concise and the pagination guidance is well structured. The opening sentence 'PerfectScale for Commitments (AWS) — commitment inventory, recommendations, and planned purchases' adds product branding and mentions recommendations/planned purchases that are not actually returned by this tool, so it does not fully earn 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 covers the essential usage aspects: what is returned, organizational scope, filtering, and the full pagination loop including termination condition. No output schema exists, but for a list endpoint this is reasonably complete; optional parameters and tenant context remain under-explained but not blocking.

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 only 14% schema description coverage, the description compensates partially by explaining the pageToken pagination loop and confirming that type and status are filterable dimensions. However, it does not explain maxResults, X-Tenant-Id, or managementAccountId beyond what the schema already provides.

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 'Returns the paginated list of Savings Plans for the specified organization' — a specific verb, resource, and scope. 'Filterable by plan type and state' further clarifies the tool's capabilities and distinguishes it from sibling tools like list_aws_reserved_instances. The opening product branding is broad, but the core purpose is unambiguous.

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 when to use the tool by specifying it returns Savings Plans for an organization and supports filtering, but it never names alternatives or states exclusions. Pagination instructions explain how to use the endpoint, not when to choose it over sibling tools like list_aws_recommendations or list_aws_planned_purchases.

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