Delete saved reply

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

Goes beyond the annotations by disclosing that the operation is local-only, takes effect immediately, and is recoverable via facebook_save_reply — this actually explains why destructiveHint=false despite being a delete. It does not describe whether deleting a nonexistent id errors or is a no-op, which matters given idempotentHint=true.

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 short sentences, front-loaded with the action and its local scope before the recovery note. Nothing is repeated from the title and every clause carries distinct 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 two-parameter local mutation with no output schema, the description covers locality, immediacy, and recoverability. The remaining gap is the shape of the returned deleted record, which the description asserts exists but does not characterize.

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 both `id` and `profile` are already documented with pattern and default-Page behavior. The description adds only the singular framing ("one local saved reply") and otherwise defers to the schema, matching the baseline for fully documented params.

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?

Names a specific verb and resource ("Delete one local saved reply") and immediately scopes it as local-only ("no Facebook call"), which distinguishes it from any Facebook-side deletion sibling. The pairing with facebook_save_reply as the inverse operation makes the boundary unambiguous.

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 supplies the restore path ("can be restored with facebook_save_reply") and the timing ("applies immediately"), which effectively tells an agent when this is safe to invoke. It stops short of explicit exclusions or a direct comparison to other delete tools, so it is clear context rather than full routing guidance.

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