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

With no annotations provided, the description carries full burden for behavioral disclosure. It implies a read-only operation by stating 'List all content pipelines' and explains output type dependencies. However, it does not address potential side effects, authorization details, pagination, or whether the list is exhaustive. This is adequate but could be more comprehensive.

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 well-structured, starting with the action and then usage cues followed by output type details. Each sentence adds value without redundancy. It could be slightly more concise by compressing the output type list but is overall efficient.

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?

Given the lack of an output schema, the description should clarify the return structure. It lists output types but does not specify fields like pipeline name, status, or created date. For a simple list tool with one parameter, the description is acceptable but not complete.

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 already described in the schema with context ('FreedomOS company id to act within...'). Schema coverage is 100%, so the description adds no extra meaning. By baseline rules, a score of 3 is appropriate.

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 clearly states the tool lists all content pipelines and enumerates the specific types (changelogs, team updates, reports, customer newsletters, social posts). It uses a specific verb ('List') and resource ('all content pipelines'), effectively distinguishing it from sibling tools like create_pipeline or archive_pipeline.

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?

The description provides explicit usage scenarios: 'when user asks about their content automation, "what content am I publishing?", "show my pipelines", or "what outputs are configured".' It also details output types with prerequisites (e.g., customer_newsletter requires Email MCP). While it lacks explicit 'when not to use' or alternatives, the guidance is clear and actionable.

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