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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds scope ('all') and clarifies dependencies (e.g., customer_newsletter requiring an Email MCP), which is useful but doesn't describe return shape, ordering, or filtering behavior.

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 longer than minimal but front-loads the core action and uses parenthetical definitions for output types rather than rambling. Trigger phrases and type explanations each earn their place, though a few parentheticals could be trimmed.

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 read-only listing tool with a single fully-described parameter and strong annotations, the description covers purpose, triggers, output types, and external dependencies. It omits return-format details, but the absence of an output schema and the simple nature of the tool make this acceptable.

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?

The only parameter, companyId, is fully described in the schema (100% coverage), including membership requirement and company-scoped context. The description adds no extra parameter detail, which is acceptable at this coverage baseline.

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 and resource ('List all content pipelines') and names five concrete output types, separating it from siblings like list_pipeline_learnings or create_pipeline. The resource is explicit and non-tautological despite the title.

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?

Provides explicit trigger phrases ('show my pipelines', 'what content am I publishing?') and scopes the tool to content automation queries. It doesn't name alternatives or exclusion conditions, but the use-case list is concrete enough to guide selection.

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