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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the trailing 'READ-ONLY' adds little. What does add value is the disclosure that only SITELINK and CALLOUT types are covered and that duplicates are a known disapproval cause, both of which affect how the agent acts on results. Pagination bounds are the remaining undisclosed trait.

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?

One front-loaded sentence led by the verb and scoped immediately, with the usage rationale attached via dashes rather than a separate paragraph. Dense but every clause carries information; the redundant 'READ-ONLY' tail is the only wasted fragment.

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?

Purpose, scope, and usage are all covered, and an output schema exists so return-format detail is not needed. The gaps are parameter documentation and any note on result limits or pagination for large accounts.

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% and the description mentions neither account_id nor customer_id, nor the relationship between the Microsoft account and the optional customer id. With two undocumented parameters and no compensating text, the agent gets no semantic guidance beyond the field names.

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?

States a specific verb (Lists) plus the exact resource (SITELINK and CALLOUT extensions attached to campaigns) and scopes it to a Microsoft (Bing) account, including what is returned (text, URLs, status). This clearly separates it from the generic list_ad_extensions, add_microsoft_ad_extensions, and remove_microsoft_ad_extensions siblings.

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?

Gives two concrete usage contexts: check before adding more (duplicates cause disapprovals) and to find the id needed for removal. That implicitly routes to the add/remove siblings. However, it never names an alternative tool explicitly and gives no when-not-to-use condition, so it falls short of a full 5.

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