compare_compute_inventory

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

No annotations provided, so description carries full burden. Explains independent sizing, cost multiplication, optional storage, and output structure. Lacks details on pricing freshness or rate limits but is sufficiently transparent.

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 concise sentences; first defines purpose, second details behavior and use case. No redundant or irrelevant 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?

Good coverage of behavior and outputs given complexity. Mentions per-row, per-cloud, and cheapest cloud results. No output schema, so description compensates well, though could clarify output format details.

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 descriptions cover many parameters (e.g., name, tier, os_disk_gb). Description adds limited extra value beyond mentioning os_disk_gb's effect. No additional parameter-specific guidance.

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 clearly states it bulk-compares compute workloads across four clouds, with specific verbs and resource. Distinguishes from siblings like 'compare_workload' (single workload) and 'compare_clouds' (generic).

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?

Implies usage for 'sizing-sheet style inputs' but does not explicitly state when to use vs alternatives or when not to use. No exclusions or alternative tool names mentioned.

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