Query ad accounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one useful scope detail ('including shared ones') but says nothing about pagination behavior, result merging, or scoping beyond what the schema and annotations supply.

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 front-loaded sentence with the verb, resource, scope, and searchable dimensions; zero filler and nothing 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?

With no output schema, the description needn't explain return values, and the rich input schema carries the parameter burden. However, for a query tool sitting among several overlapping account-listing siblings, the absence of any disambiguation leaves an agent-visible gap.

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 coverage is 80%, so the schema already documents filter, actors, roles, assets, and paging fields in detail. The phrase 'by name, ID, actor, role or asset' roughly mirrors those schema fields without adding syntax or format meaning beyond them, so the baseline 3 holds.

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 ('Search the ad accounts a business can access') and enumerates searchable dimensions (name, ID, actor, role, asset). The purpose is clear, but it never distinguishes this from the very similar siblings reddit_ads_list_ad_accounts and reddit_ads_list_business_ad_accounts, so it falls short of the 5-tier bar.

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 when-to-use guidance and no mention of alternatives, despite three near-identical siblings (list_ad_accounts, list_business_ad_accounts, get_ad_account). An agent cannot tell from the description when to reach for this query tool versus the list tools.

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