get_discount_summary

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

No annotations are provided, so the description must disclose behavior. It mentions that credentials and a specific environment variable are required. However, it does not state whether the operation is read-only, idempotent, or any rate limits. The description is adequate but could be more explicit about safety.

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 at three sentences plus a bullet-like line. The main purpose is front-loaded. The structure could be improved by separating theArgs line more clearly, but overall it is efficient and readable.

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 an output schema present, the description need not detail return values. It already lists what is returned for AWS. The tool has one optional parameter, and the description covers the prerequisite. This is sufficient for an agent to invoke correctly.

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?

The schema has one string parameter 'provider' with a default and no description. The description adds value by specifying that only 'aws' is valid now and mentioning future GCP support. This clarifies the parameter's allowed values beyond the 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 description clearly states it returns a summary of active cloud discounts, specifying AWS details (Savings Plans, Reserved Instances, Cost Explorer). The verb 'Return a summary' and resource 'active cloud discounts' are specific and distinguishable from sibling tools, none of which cover discounts.

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 explicitly mentions prerequisites: credentials and the environment variable OCC_AWS_ENABLE_COST_EXPLORER=true for AWS. It also notes that only AWS is currently supported, implying when not to use for other providers. However, it does not explicitly state alternatives or when not to use this tool.

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