Comment on a post (staged)

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

The description discloses key behavioral traits beyond the annotations: it does not actually post, it builds a preview, and it returns a confirmation_token. This explains the two-phase commit pattern, which is not evident from annotations alone.

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?

Three concise sentences, front-loaded with the core purpose and then clarifying the critical non-posting behavior. Every sentence earns its place, with no redundancy or fluff.

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?

Despite lacking an output schema, the description mentions the confirmation_token and the required follow-up (confirm_action), covering the essential output and next step. It is complete for a staged-action tool with a well-specified schema.

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?

All three parameters have detailed schema descriptions, so the baseline is 3. The description adds little beyond the schema, only reinforcing that comment_text is the exact text to be published. It does not introduce new parameter semantics.

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 opens with 'Stage a comment on a Facebook post', which is a specific verb+resource. It explicitly contrasts with actual posting by saying 'This does NOT post anything', distinguishing it from siblings like create_post and confirm_action.

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 provides clear workflow guidance: 'Show the preview to the user and call confirm_action only after they explicitly approve it.' This tells the agent exactly when to use this tool and what next step to invoke, differentiating the staging action from the committing action.

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