ghl_ad_fb_account_get

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

Annotations set readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which align with the retrieval purpose. The description adds useful behavioral context: the required OAuth scopes (adPublishing.readonly) and the API endpoint. This goes beyond annotations without contradiction.

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 and front-loaded with the purpose. It includes three brief lines (purpose, endpoint, OAuth scopes) without unnecessary fluff. Slightly longer than strictly necessary due to endpoint details, but still efficient.

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?

The tool has no output schema, and the description does not mention the structure or nature of the return data. For a simple retrieval tool with three parameters and no enums, the description could benefit from indicating what fields are in the response. The endpoint and OAuth scopes are useful, but the lack of return value information is a gap.

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 description coverage is 100%, with all three parameters (isDraft, locationId, adAccountId) already documented with descriptions and examples. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 account details' and 'Retrieve details of a specific Facebook ad account'. It specifies the verb (Get/Retrieve) and the resource (ad account details). The name distinguishes it from sibling tools like 'ghl_ad_fb_account_delete' and 'ghl_ad_fb_account_list'.

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 does not explicitly state when to use this tool over alternatives like 'ghl_ad_fb_account_list'. It provides endpoint and OAuth scopes but lacks prerequisites or exclusion criteria. The context is implied by the tool name, but no explicit guidance is given.

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