switch_profile

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

With no annotations, the description carries the full burden. It discloses the effect on subsequent posts and the requirement of a mutation template, but does not explain what happens if the template is missing or if switching back is possible. For a simple state-changing tool, this is adequate but not comprehensive.

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 two sentences, both front-loaded with the core purpose and effect. The second sentence adds a key prerequisite. No wasted verbiage, but it could be slightly more structured (e.g., separating the requirement).

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 tool with one parameter, no output schema, and no nested objects, the description covers the essential aspects: what it does, the effect on sibling tools, and a prerequisite. It is nearly complete for its simplicity, though it could clarify the exact behavior of switching (e.g., whether it's reversible).

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?

The schema has one parameter (target_id) with 0% description coverage. The tool description adds meaning by specifying it is a 'Facebook page/profile id', which clarifies the parameter's purpose beyond the schema's generic title 'Target Id'. However, it does not describe the format or how to obtain the id, leaving some ambiguity.

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 the action ('Switch the browser session'), the target ('Facebook page/profile id'), and the effect ('subsequent post_reel / post_photos go out AS that page'). It distinguishes from sibling tools like post_photos and post_reel by indicating this tool is used to set the identity for those operations.

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 explains when to use the tool (before posting as a page) and explicitly mentions a prerequisite ('Requires a captured CometProfileSwitchMutation template'). However, it does not provide exclusions or alternative tools for switching profiles, though the sibling context makes the usage fairly clear.

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