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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful context beyond that: it identifies that returned IDs are pipeline_outputs UUIDs and points to the follow-up actions approve_pipeline_item / publish_pipeline_item / request_content_revision. It stops short of describing ordering or return shape, but the annotation coverage lowers the burden.

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 description is front-loaded with the core purpose, then adds ID semantics, action routing, an exclusion with alternatives, and example queries. Every sentence earns its place and there is no redundant restatement of the title or annotations.

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 read-only listing tool with two well-documented parameters and no output schema, the description supplies the essential domain context: content pipeline outputs, UUID type, downstream action tools, and exclusions. It could have mentioned the default limit or whether results are ordered, but the schema already documents the limit default.

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 100%, so the schema already fully documents limit and companyId. The description adds no parameter-level detail beyond what is in the schema, which meets the baseline for this dimension.

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 verb and resource: 'Get CONTENT PIPELINE outputs waiting for approval/publish', and enumerates concrete item types (changelogs, newsletters, social drafts). It also explicitly distinguishes itself from Command Center decision cards, which is strong 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?

It gives explicit user-phrase triggers ('what content needs my review?', 'ready to publish?', 'approval queue' for content) and clearly names the alternative tools for Command Center decision cards. This is exemplary when-to-use/when-not-to-use guidance.

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