list_recommendations

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

With no annotations, the description carries the full burden. It discloses that the API is 607-gated on the dev account, that a null recommendation_type is rejected, and that all documented enum values fail, indicating an account/feature gating issue. This transparency about failure modes and passthrough behavior is valuable, though it omits details about return format or side effects.

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 succinct, with the core purpose in the first sentence and the key caveat following. The second paragraph repeats the gating note but adds the 'NOT live-verified' label. It is not verbose and front-loads the most important 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?

For a tool with 3 optional parameters, no output schema, and no annotations, the description is incomplete. It does not explain the role of ad_group_id and campaign_id, nor what a successful response looks like or how results are scoped. The warning about the 607 error is useful, but an agent still lacks enough context to call it safely and interpret results.

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%. The description explains the semantics and quirks of recommendation_type, but provides no information about ad_group_id or campaign_id. Since two of the three parameters are completely undocumented, the description only partially compensates for the schema gap.

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 states the tool fetches account recommendations and references the underlying MS Ad Insight GetRecommendations API. The verb 'list' is implicit in the name, and the resource is clear. It doesn't explicitly differentiate from siblings like apply_recommendation or dismiss_recommendation, but the read-only nature is evident.

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?

No guidance is given on when to use this tool versus alternatives such as apply_recommendation, dismiss_recommendation, or confirm_and_apply. The description only explains a technical quirk about recommendation_type and does not mention any logical ordering or prerequisites.

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