clean_whitespace

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

No annotations are provided, so the description must fully explain behavior. It fails to disclose what the tool does to the input, whether it is destructive, the expected return format, or any side effects. The only behavioral note is the cost, which is not about the tool's operation.

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 short but under-specified. It front-loads the name and includes cost, but the entire content is a fragment and a category label, not a structured explanation. It resembles an unfinished stub rather than a concise, informative description.

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?

With no output schema, no annotations, and only a generic parameter wrapper, the description provides almost no context for the tool's operation, inputs, outputs, or required setup. The cost is the only additional context, which is insufficient for reliable selection and invocation.

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 only defines a generic 'params' object with no specific properties, and the description offers no additional parameter details. There is no information about what keys or values the 'params' object should contain, leaving the agent without the necessary semantics to invoke the tool correctly.

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 name 'clean_whitespace' implies a specific action on whitespace, and the description labels it as a 'Text & Encoding tool,' but it does not define what 'clean' entails (e.g., trimming, collapsing, removing). This is clearer than a pure tautology but lacks the specificity needed to distinguish it from sibling tools like whitespace_analyze.

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 alternatives. The description only mentions cost, not use cases, input requirements, or exclusions. Sibling tools like whitespace_analyze or remove_accents are not referenced.

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