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

Annotations only flag destructiveHint=true and idempotentHint=false; the description goes well beyond them by disclosing exactly what is destroyed in each case (draft/scheduled will never publish; published posts lose only the Fuxux record, not the platform copy) and a concrete failure mode. This is precisely the kind of consequence detail a destructive tool needs.

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?

Four short sentences, each carrying distinct decision-relevant information: the action, the draft/scheduled consequence, the published-post limitation, and the failure case. Front-loaded with the core action and no filler.

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 one-parameter destructive tool with an output schema, the description covers everything the agent needs: side effects per post state, the key non-obvious limitation (no platform deletion), and the in-flight publishing failure. Return values are handled by the output schema, so nothing material is missing.

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?

There is a single parameter with 100% schema description coverage, and the schema already tells the agent it is a post UUID sourced from list_posts or create_post. The description adds no additional meaning about the id, so the baseline 3 applies.

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?

States a specific verb and resource ("Delete a post from Fuxux") and immediately sharpens the scope by explaining that deletion means different things for draft/scheduled vs already-published posts. An agent can distinguish this from update_post or get_post without opening any 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?

Usage is implied rather than stated: the agent learns the effect of deleting in each post state, but there is no explicit when-to-use guidance or named alternative (e.g., use update_post to unpublish, or the platform's own tools to remove a live post). The failure condition "Fails while the post is publishing" is useful operational context but is not a routing rule.

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