zernio_list_ad_accounts

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

Discloses that the tool returns IDs and status, but does not mention pagination, rate limits, or that it only lists connected accounts (not all ad accounts). Since no annotations are provided, the description carries the full burden, but the tool is simple and the description is minimally sufficient.

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?

Single sentence, to the point, front-loads the main action. No redundant information.

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 tool with no parameters and no output schema, the description adequately explains what is listed and what output to expect (IDs, status). However, it lacks information on sorting, filtering, or any potential limitations like maximum results.

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?

No parameters, so schema coverage is 100%. The description adds value by clarifying the scope ('all connected ad accounts') and the output fields ('IDs and status'), which goes beyond the empty schema.

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?

Clearly states 'List all connected ad accounts' with specific verb and resource. Specifies scope ('connected') and examples ('Facebook Ads, etc.'), which distinguishes it from sibling tools like zernio_list_accounts that may list all account types. However, 'etc.' is somewhat vague.

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?

Provides no guidance on when to use this tool over alternatives like zernio_list_accounts or zernio_list_account_groups. Does not mention prerequisites or whether the tool requires prior authentication or connection steps.

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