ad_manager_fb_set_default_page

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

Annotations indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds no behavioral detail beyond the bare action; it does not mention idempotency, side effects, or any operational constraints. It does not contradict annotations, but it fails to provide useful context like what happens if a default is already set.

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 (four words) but under-specifies the operation. It does not front-load key information like the impact or scope. Conciseness alone is not a virtue when it sacrifices essential context; this is closer to being too terse than appropriately sized.

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 mutating operation with no output schema and only two parameters, the tool description is minimal. An agent would need to infer what 'default page' means, whether it applies to a specific ad account, and what the effects are. The description is inadequate for reliable tool selection without additional context.

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 both pageId and locationId having clear descriptions in the input schema. The description adds nothing beyond the schema, which is acceptable given full schema coverage. Baseline 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 states a verb and resource ('Set default page') which conveys a specific action, but it lacks context about what a 'default page' means (e.g., for which ad account or integration). It does not distinguish it from sibling tools like ad_manager_fb_attach_page or ad_manager_fb_get_pages, but it is not a pure tautology and suggests a clear operation.

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?

There is no guidance on when to use this tool versus alternatives, no context about prerequisites (e.g., needing an existing Facebook integration), and no mention of when it should be preferred over similar set/attach operations. The description provides zero usage direction.

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