Find Idle Resources

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

Disclosures basic read-only behavior, return format (name, type, group, reason, cost), and empty list case. Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds useful return details but could mention pagination or rate limits.

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?

Three sentences, no redundancy. Front-loaded purpose, then return details, then usage guidance. Every sentence adds 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 low parameter count (1), no required parameters, comprehensive annotations, and no output schema, the description adequately covers all necessary context including return format and empty result behavior.

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?

Schema coverage is 100% with the single 'provider' parameter having a clear description and enum. The description does not add new meaning beyond the schema, so baseline 3 is appropriate.

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?

Description specifies exactly what the tool does: find provisioned but unused cloud resources (unattached disks, orphaned interfaces, unused IPs, idle VMs, empty compute plans). It clearly distinguishes from sibling tools like find_untagged_resources by focusing on idle resources.

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?

Explicitly states when to use: when user asks about waste, idle or unused resources, cleanup opportunities, or cost reduction. This provides clear context for when this tool is appropriate.

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