compare_clouds

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

No annotations are provided, but the description reveals key behaviors: best-fit SKU per cloud sorted by cost, savings calculation, and OCI free tier inclusion. It is transparent about what the tool returns.

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?

Two sentences, no redundancies. The first sentence states purpose and outputs, the second adds an important caveat. Front-loaded with key 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?

Excellent for a simple tool with two parameters: explains outputs (SKUs, costs, savings) and OCI edge case. Lacks details on return format or error handling, but adequate given no output schema.

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 0%, yet the description explicitly associates vcpus and memory_gb with the target spec, providing necessary meaning beyond the raw 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?

Clearly states the tool finds the cheapest equivalent VM across four cloud providers for a single target spec (vCPUs and memory). It distinguishes itself from siblings like compare_compute_inventory by focusing on a single spec comparison.

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 usage for single spec comparisons via 'single target spec' but does not explicitly state when to use it over siblings or provide exclusion criteria.

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