find_egress_arbitrage

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

No annotations provided, but description details return values (per-target cost, savings, payback months, recommendation) and gives concrete pricing example. Does not disclose side effects or limitations.

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?

Contains verbose example (OCI pricing) that is informative but could be more concise. First sentence is clear; rest adds context but lengthens description.

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?

Despite nested objects and 4 parameters, description lacks explanation of parameter structure (e.g., egress array format, direction enum). No output schema; behavior partially explained but input details missing.

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 description coverage is 0%; description does not explain parameters (egress, targets, one_time, source_cloud). Only indirectly references output, not input fields.

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 defines it as a specialized version of assess_migration focused on egress, with specific use cases (CDN, video streaming). Distinguishes from sibling tools like assess_migration and compare_egress.

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 data transfer is the largest cost line. Provides context but does not mention when not to use or cite alternatives.

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