discover_all_accounts

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

Without annotations, the description minimally discloses behavior: it returns a comprehensive mapping of all accessible assets. It does not detail authentication requirements, rate limits, or implications of token scope, which limits transparency.

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?

Three sentences, no waste. The most critical information is front-loaded, and every sentence adds value. Ideal conciseness.

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?

Given zero parameters, no output schema, and a simple purpose, the description is mostly complete. It could mention that it uses the current authentication context, but otherwise sufficiently covers the tool's role.

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 tool has zero parameters, so the input schema coverage is 100% by default. Per guidelines, baseline is 4. The description adds no parameter info because none exist.

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 clearly states the tool discovers all ad accounts along with their pages, pixels, and Instagram accounts. It uses a specific verb 'discover' and resource 'all ad accounts', and distinguishes itself from siblings like get_ad_accounts by mentioning associated assets.

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?

The description specifies that the tool is used to generate or update the account registry, providing a clear use case. It does not explicitly list exclusions or alternatives, but the context of sibling tools implies complementary usage.

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