compare_storage_inventory

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

Discloses key behaviors: cheapest SKU matching by disk_type, pricing formula, ignored fields (IOPS/throughput), and snapshot pricing being upper-bound. Returns per-row, per-cloud totals, and cheapest cloud. No annotations present, so description carries full burden; it meets it well.

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 with no wasted words. First sentence states purpose, second adds critical behavioral details. Front-loaded and efficient.

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 complexity (multi-cloud, many nested parameters, no output schema), the description covers purpose, pricing logic, ignored fields, and output structure. Missing explicit output format details but sufficient for an agent to understand usage.

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?

Adds meaning beyond schema: explains IOPS and throughput are metadata only, snapshot pricing details (upper-bound, incremental factor). Schema has 0% coverage on outer param, but inner properties have descriptions. Description compensates by clarifying behavioral aspects.

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 bulk-compares block-storage volumes across four clouds, specifying verb and resource. It distinguishes from siblings like compare_compute_inventory which focuses on compute.

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?

Implied usage for block-storage pricing comparison, but no explicit when-to-use or alternatives given. Does not mention when not to use or differentiate from related tools like compare_object_storage.

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