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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description's job is lighter. It still adds real value by disclosing the returned fields (id, destination, text) and the key state fact: "Nothing here is live until the owner says yes." It does not cover ordering or volume of results, which keeps it below a 5.

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 short sentences, front-loaded with what the tool returns, followed by the state caveat. The field enumeration ("id, where it would go, and the text") is slightly chatty but serves as a substitute for a missing output schema.

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?

With no output schema, the description must carry return-shape information, and it does so at a summary level: item types and the three key fields. Combined with annotations covering safety, an agent has enough to call and interpret the tool, though result ordering and pagination are unstated.

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?

The tool takes no parameters, so the baseline is 4, and the description correctly introduces no filtering concepts that could mislead. It stays silent on parameters, which is appropriate for a zero-argument tool.

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 drafts waiting for the owner's yes or no" names the resource and its state precisely, and the enumeration of posts, pages and articles sharpens the scope. It lacks an explicit verb ("list"), but the resource is still unmistakable and clearly distinct from the sibling approve_item / reject_item.

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 phrase "waiting for the owner's yes or no" implies this is the review-queue lookup that precedes approve_item or reject_item, but no alternative tool or precondition is named. An agent can infer when to call it, yet nothing explicitly excludes or routes it.

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