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

Annotations only declare the safety flags; the description adds real behavioral context beyond them — each approved post consumes the next free schedule slot and 'nothing publishes straight away', which tells the agent the effect is scheduling, not publishing. It does not cover partial-failure behavior when up to 50 IDs are passed, which matters since idempotentHint=false.

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 tight sentences, front-loaded with the action and its scheduling consequence, then the batch-limit exclusion. No filler or restatement of the title.

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 source of IDs, scheduling side effect, and the sibling alternative, with no output schema required. Missing only edge behavior — what happens if some IDs are invalid or already approved in a multi-ID request.

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?

Only one parameter with 100% schema description coverage, so the schema already documents post_ids and its pending_approvals provenance. The description restates the same provenance without adding format, ordering, or failure semantics beyond the schema.

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 (approves) and resource (posts awaiting approval in this shop), and explicitly separates itself from approve_first_batch. An agent can distinguish it from pending_approvals and reject_post purely from the description.

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?

Names the precondition (posts 'waiting for approval') and the exclusion with the exact alternative: 'Posts in the shop's first batch cannot be approved one by one: use approve_first_batch for those.' This is explicit when/when-not routing to a sibling.

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