identify_nonprod_scheduling_opportunities

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

No annotations are present, so the description carries full burden. It describes the tool as finding instances and computing savings, which implies a read-only scan. However, it does not disclose permissions, rate limits, side effects, or what happens with the instances (no scheduling action performed). This is minimal behavioral context.

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 and well-structured with a summary, Args, and Examples. It is front-loaded with the main purpose and provides necessary details without extraneous information. Every sentence contributes value.

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 tool has an output schema, the description need not detail return values. It covers the main use case, parameter explanations, and example queries. It could mention time constraints or filtering by tags, but overall it is sufficiently complete for a discovery tool.

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?

Although schema coverage is 0%, the description adds meaningful parameter explanations in the Args section: 'regions' defaults to all opted-in regions, 'max_results' defaults to 50. This adds clarity beyond what the schema provides (types and defaults only). Detailed guidance enhances usability.

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 finds non-production EC2 instances running 24/7 and identifies savings opportunities. It specifies the resource type (EC2) and context (dev/staging/test), distinguishing it from sibling audit tools that target other resources or waste types.

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 includes example queries that explicitly indicate when to use the tool, such as 'Find non-prod instances we could schedule to save money'. It implies usage context (cost savings for non-production). However, it does not provide explicit when-not-to-use scenarios or mention alternatives.

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