Set Active Page

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

The description adds valuable behavioral context beyond the annotations: it explains that cookie scraping acts as the imported account, and that this tool merely records a Page without switching identity. While the destructiveHint annotation is not contradicted or elaborated on, the description provides useful non-obvious details about its effect on session state.

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 compact and front-loaded with the core purpose in the first sentence. The subsequent note is useful but slightly verbose, containing tangential context about cookie scraping that could be tightened without losing essential information.

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 niche state-setting tool with an output schema and destructiveHint annotation, the description is thorough. It explains the purpose, its limitations (no identity switching), and the context for Page-mode sessions, making it complete enough for an agent to use correctly without needing to guess.

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%, so the parameters page_id and page_name are already well-documented. The description does not add any parameter-specific meaning, staying at the baseline 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 clearly states it 'persists the active Facebook Page for display/context purposes', using a specific verb and resource. It distinguishes itself from account-switching tools by explicitly noting it does not switch the acting identity, and from other Page-related tools by focusing on bookkeeping and context.

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?

It gives clear context for when to use the tool (display/context, agent bookkeeping, Page-mode sessions) and an important exclusion ('does not switch the acting identity'). However, it does not explicitly name alternative tools like switch_active_account, leaving the agent to infer the alternative from the sibling list.

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