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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no indication of case sensitivity, whether matching is exact or substring, whether the result is boolean or a list of hits, or whether the operation is a pure read. For a 4-parameter predicate tool this is a complete failure to disclose behavior.

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?

It is short, but the brevity comes from under-specification rather than economy: the single fragment repeats the tool name twice and contains zero information. Nothing is front-loaded because there is nothing to front-load.

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?

A 4-parameter tool with no annotations, no output schema, and a tautological description leaves the agent with nothing to reason from. Every dimension an agent needs — semantics, matching rules, return shape, argument roles — is absent.

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 nominally 100%, but every parameter description is a vacuous placeholder ("Text to process", "Input to process", "Values to process", "Substrings to process") that conveys no meaning. Neither the description nor the schema explains the roles of text vs input vs values vs substrings, so an agent cannot tell which fields to populate or how they relate.

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?

"Contains Any: Contains Any" merely restates the tool name and adds no verb+resource information. It never says whether it tests a text for the presence of any candidate substring, or what it returns. An agent cannot distinguish it from siblings like x402-words-containing, x402-line-contains, x402-starts-with-any, or x402-ends-with-any.

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 when-to-use, when-not-to-use, or alternative-tool guidance of any kind. The crowded sibling set (x402-starts-with-any, x402-ends-with-any, x402-words-containing, x402-line-contains) makes routing guidance essential, and none is provided.

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