list_content_pipeline

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

With no annotations, the description carries the full behavioral burden. It signals a read-style operation and explains the content of the result, but doesn't say whether it returns item records or only aggregates, nor how pagination via 'limit' interacts with the counts shown. No permission or rate-limit context either.

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 well-formed sentence with the resource stated up front and a concrete illustrative example. The example is the only arguable extra, but it clarifies the output shape, so nothing is wasteful.

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 list tool with no required parameters, full schema coverage and no output schema, the description is nearly adequate. The remaining gap is the tension between 'queued items' and 'counts and progress' — an agent can't tell whether it gets rows or aggregates.

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 100%, so every parameter is already documented in the schema, setting the baseline at 3. The description adds no extra meaning about the filters (stage, accountId, workspaceId) or how limit applies to the counts.

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 names a specific verb ('Returns'), a clear resource ('queued items in the SocialDispatch content pipeline') and even characterizes the payload ('counts and progress'). It never distinguishes itself from siblings like get_next_pipeline_item or list_recent_posts, so an agent must infer the boundary from the name alone.

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?

There is no statement of when to call this versus the closely related siblings (get_next_pipeline_item for acting on the next item, update_content_progress for advancing items, add_content_ideas for enqueueing). Usage is only implied by the word 'queued', leaving the agent to guess.

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