blackmount-nlp-mcp

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

With no annotations provided, the description carries full burden but only lists cleaning steps without disclosing behavioral traits. It doesn't mention whether the pipeline is order-dependent, if steps are optional/configurable via the 'steps' parameter, what happens with null steps, or output format details. For a configurable tool with 2 parameters, this is inadequate.

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 appropriately sized and front-loaded with the core purpose. The list of steps is efficient, though it could be structured more clearly (e.g., as a bulleted list in practice). No wasted sentences, but minor improvements in formatting are possible.

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 2 parameters with 0% schema coverage, no annotations, but an output schema exists, the description is partially complete. It covers the pipeline concept and steps but lacks details on parameter usage, behavioral context, and differentiation from siblings. The output schema reduces the need to explain return values, but more guidance is needed for effective tool selection.

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 0%, so the description must compensate. It implies the 'steps' parameter controls which cleaning steps to apply (listing them), adding meaning beyond the bare schema. However, it doesn't explain the 'text' parameter or provide details on step ordering, defaults, or format, leaving gaps in parameter understanding.

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 performs 'configurable cleaning pipeline' with specific steps listed (html, urls, emails, etc.), providing a specific verb ('clean') and resource ('text'). However, it doesn't explicitly differentiate from sibling tools like clean_lowercase or clean_remove_html that handle individual steps, missing full sibling differentiation.

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?

No guidance is provided on when to use this tool versus the many sibling cleaning tools (e.g., clean_lowercase, clean_remove_html). The description lists steps but doesn't explain context, prerequisites, or alternatives, leaving the agent without usage direction.

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