Edit a post

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

The description adds a meaningful side effect beyond the annotations: 'Facebook shows an edit history to viewers.' This tells the agent that edits are permanent in the public record, which complements the non-destructive and open-world annotations. It does not mention auth or rate limits, but it does disclose a key behavioral consequence.

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?

Two short, front-loaded sentences with no filler. The core action is stated first, and the edit-history note earns its place as essential behavioral context.

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?

The description is adequate for understanding the basic update operation, and the edit-history note adds context. However, it omits what the tool returns, any permissions required to edit a Page post, and whether only text is editable or other fields are affected. For a mutation tool with no output schema, this is a noticeable gap.

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 description adds no parameter-specific meaning beyond what the input schema already provides. The schema covers message and page, but post_id has no description and the tool description does not fill that gap or clarify constraints, defaults, or formats.

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 names the exact action and resource: 'Change the text of a published post.' This distinguishes update_post from siblings like create_post, delete_post, and publish_draft, and makes the tool's unique role clear.

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?

No guidance is given about when to use this tool versus alternatives, nor are exclusions or prerequisites stated. Usage is implied by the verb 'Change,' but the description does not actively route the agent away from create_post or publish_draft when appropriate.

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