ghl_ad_fb_page_set_default

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

The description adds little beyond annotations: it mentions the endpoint and OAuth scopes but does not explain side effects (e.g., replaces any existing default? only one default per location?). Annotations cover idempotency and non-destructiveness, but the description misses behavioral details.

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. The endpoint and scopes are supplementary but not verbose. It could be slightly tighter by omitting the endpoint line, but it remains 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?

Given the tool has 3 parameters including a nested object and no output schema, the description should clarify behavior like whether setting a default overwrites an existing one. It lacks this operational context, leaving gaps for the agent.

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 the schema already describes all parameters thoroughly. The description adds no additional meaning beyond what is in the schema (e.g., it does not clarify the relationship between locationId and pageId).

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 explicitly states 'Set default page' and 'Set the default Facebook page for a location', clearly indicating the verb (set) and resource (default Facebook page) with a specific scope (for a location). This distinguishes it from sibling page operations like listing or deleting.

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 provides no guidance on when to use this tool versus alternatives such as ghl_ad_fb_page_list or ghl_ad_fb_page_delete. It does not mention prerequisites, conditions, or when not to use it.

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