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

Annotations already flag destructiveHint and idempotentHint, but the description adds substantive context beyond them: irreversibility, the human-approval gate, that the post is NOT removed from connected social platforms, and that analytics data is dropped with the record. Those are exactly the consequences an agent needs before committing a destructive call.

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, zero filler, ordered by importance: what it does, then the irreversibility plus approval gate, then the consequences by post state. Each sentence changes how an agent would call the tool.

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?

Fully adequate for a 3-required-param destructive tool with no output schema: the agent knows the action, the safety gate, and the downstream effects on platforms and analytics. Nothing material is missing to invoke it correctly.

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 67% and confirm already carries its own description in the schema; the description only restates "pass confirm: true" without adding format or constraint detail. postId and projectId get no semantic treatment in the description beyond the schema's list_projects hint, so baseline 3 is appropriate.

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?

Specific verb+resource ("Deletes a post from Simplo") plus a scoping clause that separates it from sibling mutations like unschedule_post and update_post by explaining what actually happens to the record and its analytics. An agent can distinguish it from the rest of the post lifecycle tools without opening a schema.

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?

Gives an explicit precondition ("ask the user first, then pass confirm: true") and clarifies the scheduled-vs-published outcome, which is exactly the ambiguity that leads agents to confuse this with unschedule_post. It stops short of naming unschedule_post as the non-destructive alternative, so the routing is implied rather than stated.

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