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

Annotations already declare readOnlyHint=false and destructiveHint=true, indicating a write operation with possible side effects. The description adds the write-tier approval note ('first use may require a manager's approval...'), which is valuable operational context not present in annotations. It doesn't detail exact side effects or what gets destroyed, but the approval disclosure covers a key behavioral aspect.

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 moderately long but well-structured: core purpose, usage triggers, output types, and an approval note. It is front-loaded with the main action and trigger examples. Each sentence contributes useful information, though the output-type enumeration adds some length. It remains clear and scannable.

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 5-parameter tool with a nested object and no output schema, the description covers usage triggers, output types, and the approval workflow. The schema documents companyId membership requirements, and the description explains the output semantics. It doesn't describe the return value or post-creation steps, but those are not critical for invoking the tool. It is sufficiently complete for an agent to call it correctly.

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 every parameter is documented. The description adds extra semantics for the output parameter by elaborating on each output type (e.g., team_update is internal email via FreedomOS, customer_newsletter requires Email MCP), which goes beyond the schema enum text. It doesn't add much for name, persona, or companyId, but the incremental value on output justifies a 4.

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 ('Create a new content pipeline to automate content creation') and resource, and lists concrete output types and example user intents. It distinguishes from siblings like update_pipeline by focusing on creation. The description clearly tells an agent what this tool does and when it applies.

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 ('Use when user says "set up a changelog", "create a newsletter pipeline"...') and describes the automation use case. It doesn't explicitly mention exclusions or alternatives (e.g., update_pipeline for existing pipelines), but the trigger conditions are unambiguous, so an agent can confidently select this tool for creation requests.

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