ad_manager_fb_get_ad_accounts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no additional behavioral context, such as that this returns a list, supports pagination, or requires pre-existing integration – leaving the agent without insight into what the call actually does beyond a generic fetch.

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 no unnecessary words, making it efficient. However, it is so minimal that it sacrifices informative value, though it remains appropriately short for a simple read operation.

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 5 parameters, pagination controls, and no output schema, the description is incomplete. It lacks any indication of return structure, usage context, or differentiation from related tools, making it harder for an agent to invoke it correctly in practice.

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 covers 100% of the 5 parameters with descriptions, so the schema already documents each parameter. The description adds no extra meaning beyond what the schema provides, warranting the baseline score for high schema coverage.

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 'Get ad accounts' states a clear verb and resource, but it does not specify that it is Facebook-specific or differentiate it from the singular sibling ad_manager_fb_get_ad_account or the Google/LinkedIn equivalents. Without the tool name, the scope is ambiguous.

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 provided about when to use this tool versus the singular get_ad_account or other platform-specific account listers. The description does not mention key features like pagination or filtering options, leaving the agent without context on how to choose the right tool.

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