discover_all_accounts

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

No annotations are provided, so the description carries the full burden. It states the tool returns a 'comprehensive mapping of all accessible assets', implying it is a read operation, but does not explicitly disclose whether it modifies state, requires special permissions, or has rate limits. The description is adequate but could be more transparent about side effects.

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 extremely concise with three sentences, each adding distinct value: the first describes the action, the second the use case, and the third the output format. No redundant or extraneous text, and the key information is front-loaded.

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 the tool has no parameters, no output schema, and no annotations, the description provides a clear purpose, use case, and output description. It could mention whether it is read-only or idempotent, but overall it is complete enough for an agent to understand when and how to invoke it.

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 has zero parameters, so schema coverage is effectively 100%. The description does not need to explain parameters. A score of 4 reflects that no additional parameter information is required, and the description is not penalized for lacking param details.

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. The verb 'discover' and resource 'all ad accounts' are specific, and it distinguishes from sibling tools like 'get_ad_accounts' which likely only lists accounts without the comprehensive mapping.

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 explicitly says it is used to generate or update the account registry ('config/accounts.yaml'), providing a concrete use case. It implicitly guides when to use this tool versus simpler list tools like 'get_ad_accounts' by mentioning the comprehensive mapping, though it lacks explicit when-not-to-use guidance.

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