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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: the ordering (newest first), the authorization requirement that `approve` is not implied by admin, the Agency-plan gate, the fields returned in rejected mode, and the underlying endpoint. These are exactly the constraints an agent needs before calling an approval-scoped endpoint.

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?

The bracketed read-only marker and the list of content types are front-loaded, and every clause carries new information: scope, mode switch, returned fields, prerequisites. The endpoint parenthetical is compact and adds integration context without padding.

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 two-parameter, no-output-schema read tool, this covers mode semantics, prerequisites, ordering, and return fields, so an agent could call it correctly. The only material gap is the unexplained `brandId` filter, which leaves the agent guessing whether to scope the call to a brand.

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 description coverage is 0%, so the description has to carry the parameter burden. It does well for `status`, documenting the pending default and the behavioral switch to rejected content, but `brandId` is never mentioned anywhere in the description or the schema. Half the parameters are therefore effectively undocumented.

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?

It names a specific verb and resource, then enumerates exactly what is listed: posts with publish requiresApproval:true, drafts submitted for review, and workflow runs parked at an approval gate. The `kind` values (manual/workflow) and the rejected-mode behavior further pin down the scope, so an agent can distinguish this listing tool from the sibling decide_approval or list_reviews without opening the schema.

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?

It explains the two operating modes clearly: default status returns pending items, while status "rejected" switches to rejected content carrying reviewer reason (`note`, `reasonChips`), rejecter and timestamp. It also states the prerequisites (explicit `approve` scope, Agency plan). It does not name alternative tools or say explicitly to use decide_approval when the intent is to act rather than read, so it falls short of full when/when-not routing.

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