get_azure_advisor_recommendations

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

No annotations exist, so the description must disclose behavior. It explains the tool returns recommendations with savings, orders by highest savings, and has a default limit of 100. However, it does not mention authorization requirements, rate limits, or side effects (likely read-only).

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 concise with two paragraphs, a structured 'Args' section, and relevant examples. It is front-loaded with purpose and provides necessary details without redundancy.

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?

For a tool with no output schema and two simple parameters, the description covers the essential aspects. It could improve by detailing the return structure beyond mentioning savings figures, but it is largely complete.

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?

The description adds meaningful context to both parameters: subscription_id is explained as a single Azure subscription or all configured subs when null, and limit is described with default and ordering (highest savings first). This compensates for the 0% schema description coverage.

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 retrieves Azure Advisor cost recommendations, specifies the types (VM rightsizing, idle resource cleanup, reservation/savings-plan purchases), and notes that savings are pre-computed. It also draws a parallel to AWS Compute Optimizer, making the purpose distinct and unambiguous.

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 implies the tool is for cost optimization recommendations but does not explicitly compare it to alternatives or state when not to use it. Sibling tools like get_azure_budgets or get_azure_cost_by_dimension exist, but no guidance on selection is provided.

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