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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the '[read]' prefix adds nothing new. The description does not disclose pagination behavior, default page size, ordering, or what an empty result means for a 10-param list endpoint.

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?

A single dense sentence that front-loads the operation and the provider enumeration before the filter list. No filler, no restatement of the title.

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?

The filter surface is well covered and annotations handle the safety profile, but for a paginated list tool with no output schema the description says nothing about pagination, result volume, or accepted status values, leaving real gaps an agent must guess at.

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?

With 0% schema description coverage, the description carries the load and does explain 7 of 10 parameters: provider, status, website, customer and grant filters, plus the 'id or uuid' pairing that clarifies why both variants exist. It leaves page/per_page unmentioned, but those are self-evident from names and defaults.

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 and resource ('List connected ad accounts') and enumerates the supported providers, which makes the target object unambiguous against siblings like list_ads_campaigns or list_ads_alerts. It does not explicitly name a sibling or contrast scope with them, so it falls short of a 5.

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 phrase 'optionally filtered by provider, status, branch website, customer or grant' implies the intended use case (browse/filter the account inventory), but there is no statement of when to prefer this over sibling listing tools or of any prerequisites. Usage is inferable rather than guided.

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