clean_text_pipeline

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

With no annotations, the description should disclose behavior beyond the basics. It lists the steps but does not explain the order of application, whether steps are cumulative, or any side effects like text mutability.

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 a single concise sentence with a colon-separated list, containing no unnecessary words.

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 configurable pipeline complexity and missing annotations, the description provides a list of steps but lacks details on pipeline behavior (order, defaults, interaction). It is adequate but not fully 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 schema has 0% description coverage, but the description adds meaning by enumerating the possible steps (html, urls, etc.). However, it does not clarify that the 'steps' parameter can be null to use defaults or the exact format expected.

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 it is a configurable cleaning pipeline and lists the specific steps (html, urls, emails, etc.), distinguishing it from sibling tools that perform individual cleaning operations.

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 implies the tool is for applying multiple cleaning steps in sequence but does not explicitly state when to use it versus the individual cleaning tools or provide any usage restrictions.

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