list_ad_accounts

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

Discloses pagination and the scope of accessible accounts, but with no annotations, it omits details like authentication requirements, rate limits, or default fields returned. The mention of pagination adds some behavioral context beyond what the schema hints.

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?

Two concise, front-loaded sentences with no wasted words. The key verb and resource appear immediately, and pagination is noted without verbosity.

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 simple list tool with no output schema, the description covers the basic purpose and pagination, but doesn't explain the return object structure or differentiate from similar list tools like list_business_ad_accounts. It is adequate but has clear 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 input schema provides 100% coverage with descriptions for all three parameters (after, limit, fields). The tool description adds no additional semantic meaning beyond what the schema already states.

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 uses a specific verb ('List') and resource ('ad accounts'), and clarifies scope ('accessible by the current user'), distinguishing it from siblings like get_ad_account or list_business_ad_accounts.

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?

Clearly states the context (all ad accounts accessible by the current user) and that results are paginated, but does not explicitly mention when to use this over alternatives or when not to use it.

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