approve_draft

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

Discloses execution path and idempotency (once-only), but the annotations' destructiveHint=false may conflict if execution is destructive; description does not clarify.

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 concise sentences front-load the action and add key constraints without fluff.

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?

Covers purpose and usage well; output schema exists for return values. Lacks detail on what 'execute' entails but sufficient for a simple tool.

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?

Single parameter with no schema description, but description adds meaning by stating behavior for unknown/consumed ids, raising baseline from 1 to 3.

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 clearly states the tool executes a pending draft created by a write tool, distinguishing it from siblings like reject_draft and list_drafts.

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?

Provides context for when to use (after a write tool creates a draft) and includes constraints (approve once, error on invalid ids). Could explicitly contrast with reject_draft.

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