list_ad_accounts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The parenthetical reveals an approval requirement but does not state what happens when approval is missing (error vs. empty list), whether authentication is needed, or any pagination/rate-limit behavior. The output schema partially covers return values, but critical operational behavior is left undisclosed.

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?

The description is very short and front-loaded, which is structurally efficient. However, the vague parenthetical raises an important question about approval requirements without answering it, making the text feel under-specified rather than deliberately concise.

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 tool is simple (one optional parameter) and has an output schema, which eases the return-value burden. However, the approval gate is a central usage barrier that is entirely unexplained—an agent cannot determine how to satisfy it, what failure looks like, or which sibling tool to consult first.

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 adds no meaning to the single 'path' parameter beyond what the schema already provides via its default value '/rest/adAccounts'. The description fails to compensate for the schema's lack of parameter documentation.

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?

'List ad accounts' is a specific verb plus resource, clearly conveying the tool's core action and distinguishing it from sibling tools like list_campaigns and list_capabilities. The parenthetical '(approval-gated capability)' introduces a constraint hint but does not obscure the primary purpose.

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 guidance is given on when to use this tool versus alternatives or what prerequisites exist. The approval-gated note implies access limitations but never explains how to check approval (e.g., via can_execute_tool) or whether authentication via the auth_* siblings is required first.

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