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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact — results are conditional on the org's approval workflow being enabled — but says nothing about pagination, result volume, or what an empty list means, which is modest added value on top of the annotations.

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?

A single front-loaded sentence with no filler, and the scoping condition is placed where it is read first. It is efficient, though it is terse enough that it omits useful context rather than being padded.

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, fully-annotated read tool with no output schema and a single fully-documented parameter, the description covers the essential purpose and the enabling condition. Only secondary details (pagination, ordering, empty-result semantics) are absent, which is a minor gap.

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?

There is a single optional parameter with 100% schema description coverage; the schema already explains workspaceId, its provenance (list_workspaces), and its fallback behavior. The description adds no parameter-level meaning, so the baseline of 3 applies.

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 resource ('Posts waiting for review') and scopes it with a condition ('when the approval workflow is enabled for this organization'), which lets an agent distinguish it from a generic list_posts. It never names the close sibling list_pending_reels or otherwise draws an explicit boundary, so it stops short of full sibling differentiation.

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?

Usage is only implied: the tool is relevant when the approval workflow is enabled. There is no explicit when-to-use/when-not framing and no routing to alternatives like list_pending_reels or review_post, leaving the agent to infer the selection criteria.

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