Update Comment

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

Annotations indicate a mutation (readOnlyHint=false) that is idempotent and non-destructive; description confirms an edit operation. Additionally, description adds the behavior of rejecting Instagram IDs instead of failing silently, which is valuable beyond annotation fields.

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 sentences, no wasted words. First sentence immediately states purpose, second adds critical platform constraint. Efficient and front-loaded.

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?

Given sibling tools like delete_comment, create_comment, etc., the description adequately distinguishes update_comment. It has no output schema, so return values are not described, which is acceptable for a mutation tool. Could mention if it returns the updated comment object, but not necessary for completeness.

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 coverage is 100%, so baseline is 3. The description adds context about platform auto-detection from ID shape, which is not in the schema but aids agent understanding. However, it doesn't elaborate on the message parameter beyond the schema description.

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?

Description clearly states 'Edit the text of a comment the Page authored.' The verb 'edit' maps directly to the tool name, and the resource is specified as comment text. It also implicitly distinguishes from sibling tools like delete_comment or create_comment.

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?

Explicitly states 'FACEBOOK ONLY' and explains that Instagram has no edit operation, so this tool rejects Instagram IDs. This gives clear when-to-use and when-not-to-use guidance, including behavior on invalid input.

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