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

The annotations already indicate destructiveHint=true and readOnlyHint=false, signaling a write/delete operation. The description adds the context that the resource is a 'scheduled post', but does not elaborate on whether cancellation deletes or merely unschedules the post, nor does it mention authorization requirements or side effects.

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?

The description is a single sentence, which is concise but insufficient. With six parameters, nested objects, and no output schema, one sentence cannot adequately inform the agent. The structure is front-loaded but lacks necessary detail.

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 the tool complexity (6 parameters, 2 required, nested objects, no output schema) and the presence of a confusingly similar sibling, the description is severely incomplete. It does not explain the workflow, return values, or how the idempotency key should be used, leaving the agent underinformed.

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 only 50%, and the description does not mention any parameter. It fails to clarify the purpose of key parameters like 'id' (the post UUID) and 'idempotency_key', nor does it explain the meaning of nested objects 'body' and 'query'. The description should compensate for the sparse schema but does not.

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?

The description states the verb 'Cancel' and resource 'scheduled post', clearly indicating the tool's function. However, there is a sibling tool named 'aidelly_cancel_scheduled_post' which performs a very similar action, and the description does not differentiate between them, causing potential confusion.

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 provides no guidance on when to use this tool versus alternatives, such as the overlapping sibling 'aidelly_cancel_scheduled_post' or other post-related tools. No context about prerequisites or post-cancellation effects is given.

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