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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description nevertheless adds ordering semantics and the meaning of the `canApprove` per-item field relative to THIS connection, which is genuinely useful context. It omits pagination/result-size behaviour, keeping it short of 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 tight sentences with the resource and scope front-loaded and no filler; the only slight redundancy is the '[read-only]' tag, which the annotations already declare.

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 three undocumented filter parameters and no output schema, the description only partially covers what an agent needs; it surfaces one return field (canApprove) but leaves filtering behaviour and result shape otherwise unaddressed.

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 coverage is 0% and the description explains none of the three parameters. The `window` enum is especially cryptic — "in" versus "upcoming" versus "all" is not decipherable without prose, and the default status of 'pending' versus 'all' likewise goes unmentioned.

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 (list) and resource (scheduled-post reviews awaiting human sign-off) and adds ordering ('oldest slot first'). It does not explicitly distinguish itself from the close siblings list_approvals and list_publish_actions, so an agent must infer the boundary.

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 implied rather than stated: the mention of `canApprove` hints that decide_review is the follow-up action, and 'waiting for (or given) sign-off' suggests the review stage. There is no explicit when-to-use, when-not, or named alternative versus list_approvals.

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