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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds real value by clarifying that the delete is local to Ignix/scheduler and does NOT remove the network copy — a genuinely non-obvious side effect. It stops there, saying nothing about permissions or cascade behavior for scheduled entries.

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, front-loaded with the core action and then the critical caveat. Every clause earns its place and no filler is present.

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 destructive mutation with no output schema, the annotations carry the safety profile and the description covers the main ambiguity (network vs. local effect). It would be stronger if it distinguished itself from unschedule_post and noted what happens to an already-scheduled post, but nothing essential to correct invocation 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?

Schema coverage is 50%: idempotencyKey is fully documented in the schema with format rules and retry semantics, while postId carries no description. The description adds no parameter detail of its own, so it neither compensates nor detracts; the one undocumented param is a self-evident post identifier.

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 (Delete) and resource (a post), and immediately scopes it: 'from Ignix and from the scheduler,' which rules out ambiguity about what is being deleted. It also names the sibling it is not (unpublish_post), so an agent can distinguish it without opening either 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 when-not condition tied to an alternative: if the post is already live on the network, use unpublish_post instead. This is exactly the routing decision an agent needs, stated in one clause.

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