get_savings_ledger

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

No annotations are provided, so the description must convey behavior. It implies a read operation ('Shows') and describes parameters, but it does not disclose pagination, performance, or output format details beyond what is implied.

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 concise, uses bullet points for parameters, and front-loads the purpose. Every sentence is relevant, with no extraneous information.

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?

Given the simple input schema (2 optional params), no annotations, and the existence of an output schema, the description adequately covers purpose and parameter semantics. It could clarify the output structure slightly, but the output schema likely fills this gap.

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 0% schema description coverage, the description adds meaningful parameter explanations: 'days: Lookback window... Filters by generated_at' and 'account_id: Filter to a specific cloud account ID. None = all accounts.' This compensates well for the lack of schema 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 tool shows a 'clean summary of savings found, acted on, and verified,' using a specific verb and resource. It provides example user queries, which help distinguish it from siblings like get_savings_summary, though it could further differentiate.

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?

A 'Use when' section lists example user queries, giving clear context for when to invoke. However, it does not explicitly state when not to use or mention alternative tools like get_savings_summary, which would strengthen guidance.

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