ghl_ad_fb_account_list

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral context beyond annotations: endpoint details, version header, OAuth scopes, and pagination behavior. No contradictions with annotations.

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 concise with 5 lines, each adding relevant info: title, clarification, endpoint, scopes, pagination. No wasted words, but could be more structured (e.g., bullet points).

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?

With 5 parameters and no output schema, the description explains pagination but lacks details on 'type' and 'fetchAll' parameters. Response structure is not hinted at. Adequate but not complete for a list tool with multiple optional filters.

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 coverage is 100%, so baseline is 3. The description mentions pagination params (limit) but does not explain other parameters like locationId, next, type, or fetchAll. Adds some value but insufficiently covers all parameters.

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 'Get ad accounts' and 'Retrieve Facebook ad accounts available for the connected user', specifying the resource (Facebook ad accounts) and action (list). This distinguishes it from sibling tools like ghl_ad_fb_account_get which retrieves a single account.

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 mentions pagination params and OAuth scopes but does not explicitly state when to use this tool versus alternatives. Usage is implied via context of sibling tools, but no direct guidance on when-not or alternatives is provided.

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