estimate_migration_savings

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent knows the tool is safe and idempotent. The description adds minimal behavioral context beyond confirming the calculation nature. It does not disclose what 'savings' entails (e.g., monthly cost difference, total cost of ownership), leaving some ambiguity.

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?

The description is a single, clear sentence with no filler. It is front-loaded and conveys the core purpose efficiently. However, it could be slightly expanded to include more context without becoming verbose.

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 tool's moderate complexity (5 parameters with nested objects, no output schema), the description is incomplete. It does not explain return values, required versus optional parameters, or the scope of the savings calculation (e.g., monthly vs. annual). The schema descriptions cover only 40% of parameters, and the description fails to fill the gaps.

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 low at 40% (only 'currentProvider' and 'targetProvider' have descriptions). The description does not mention any parameters or provide additional context for the nested objects (compute, storage, egress). The parameter names are somewhat self-explanatory, but the lack of description compensation results in poor semantics.

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 the tool's purpose: 'Calculate potential savings when migrating from one cloud provider to another.' It uses a specific verb ('calculate') and resource ('potential savings when migrating'), which distinguishes it from siblings that might only calculate costs or compare individual services. However, it does not explicitly differentiate from similar tools like 'calculate_workload_cost' or 'quick_estimate', which could overlap.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical use cases, or when not to use it. Given the presence of many sibling tools with overlapping functionality (e.g., 'compare_compute', 'quick_estimate'), this lack of usage context is a significant gap.

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