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

No annotations are provided, so the description carries the full burden. It states 'Show the style guide and recent revision history', indicating a read-only operation. However, it does not disclose any additional behavioral traits such as pagination, auth specifics, or what exactly constitutes 'recent'. Given zero annotation coverage, the description is adequate but lacks depth.

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 two sentences: the first concisely states the purpose, and the second provides example usage scenarios. Every sentence adds value, with no redundancy. It is front-loaded and 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 3 parameters and no output schema, the description covers the core functionality. It mentions what the tool shows and when to use it. However, it does not specify the format of the output (e.g., list or text) or define 'recent'. Slightly incomplete but mostly adequate for a list tool.

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% with descriptions for all three parameters (companyId, pipeline_id, output_format). The description does not add extra meaning beyond the schema, so baseline 3 is appropriate. It mentions the tool's purpose but no additional parameter semantics.

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 shows 'style guide and recent revision history' for a content pipeline. It provides specific example user queries, making the purpose very clear. However, it does not explicitly differentiate from sibling tools like 'update_pipeline_style_guide' or 'clear_pipeline_learnings', lacking direct sibling distinction.

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 explicitly tells when to use the tool with example user queries ('what are the learnings for my newsletter?', 'show me the style guide', etc.), providing clear context for invocation. It does not mention when not to use or alternative tools, but the examples guide the agent adequately.

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