meta_list_ad_accounts

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — results include Business Manager-owned accounts, not just directly owned ones — but says nothing about pagination, truncation at the default limit of 200, or rate limits.

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 sentence, front-loaded with the verb and resource, with the scope qualifier in parentheses. Nothing is wasted and nothing is buried.

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?

An output schema exists, so return-value shape need not be described, and with a single optional parameter the tool is simple. Still, for a paginated, permission-dependent listing tool the description omits result-cap behavior and any routing to sibling listing tools, leaving real gaps.

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 single parameter 'limit' has 0% schema description coverage, so the description is the only place it could be explained — and it is not. Worse, 'List every Meta ad account' implies a complete enumeration while the default limit of 200 silently caps results, so the description actively creates a misleading expectation about result completeness.

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?

Names a specific verb and resource (list Meta ad accounts) and adds scope that matters: 'every ... the token can access (including via Business Managers)'. This distinguishes it in substance from meta_list_entities and google_ads_list_accounts, though it never names those siblings explicitly.

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?

Usage is only implied — an agent can infer this is a discovery/enumeration step, but the description gives no explicit when-to-use, when-not, or pointer to meta_list_entities for other object types. No prerequisites (token scope, Business Manager permissions) are stated.

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