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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is established. The description adds meaningful behavioral context beyond annotations by stating that rejected drafts are not posted and cannot be approved later, making the irreversible consequence clear.

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 two short sentences and front-loads the action before the irreversible consequence. There is no unnecessary wording.

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 simple destructive mutation, the annotations and description together cover the key safety consequence: rejection is permanent and prevents later approval. However, the only parameter is completely undocumented in both the schema and the description, so an agent lacks guidance on how to supply valid draft IDs.

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 description coverage is 0% for the single required postIds array, and the description does not explain what the IDs refer to, where to obtain them, or the 1–20 item constraint. The phrase 'saved drafts' only weakly implies the parameter semantics.

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 a specific verb and resource: 'Reject saved drafts.' It is clearly distinguishable from approve_drafts and save_drafts by implication, though it does not explicitly name sibling alternatives.

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 implies when to use it by explaining that rejected drafts are not posted and cannot later be approved, which distinguishes rejection from saving or approving. However, it gives no explicit when-to-use guidance, prerequisites, or named alternatives.

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