azure_calculate_cost

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds that it 'looks up pricing and calculates estimated monthly cost', which is consistent. It does not discuss accuracy, caching, or data freshness, but overall transparency is good.

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 well-structured with examples and a parameter list, but it redundantly repeats schema descriptions. The examples are helpful, and the front-loading is effective. Some pruning could improve conciseness.

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 no output schema, the 'Returns' line provides minimal description of return type. The tool has 8 parameters with one required, and the description covers use cases adequately. It could mention that cost components are returned, but it's sufficient for selection and invocation.

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 100%, and the description adds value by providing examples that clarify parameter usage (e.g., hours_per_month=1 for storage, defaults like 730 hours). The examples demonstrate how parameters interact, going beyond mere schema descriptions.

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 'Calculate monthly cost for an Azure resource' and provides examples that differentiate it from siblings like azure_fetch_prices and azure_query_prices, which focus on raw price lookups. The verb 'calculate' and the resource 'Azure resource' are specific.

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?

Examples illustrate typical usage (e.g., VM cost, storage cost) but do not explicitly state when not to use it or mention alternative tools like azure_query_prices for raw price retrieval. The guidance is clear but lacks exclusion criteria.

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