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 does not state the return shape (presumably a boolean), what happens with empty or missing inputs, or whether 'text'/'input' are aliases. The only behavioral disclosure is billing boilerplate ('5 free trial calls per signed wallet'), which hints at a paid rate limit but is marketing text rather than operational context.

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?

A single short, front-loaded sentence with no padding; the eligible content is compact and readable. The 'Ends With Any:' prefix mildly restates the tool name, and the emoji/promo tail is noise, but the size is appropriate.

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?

For a tool with four undocumented, non-required string parameters, no annotations, and no output schema, the definition is too thin. It omits required-input behaviour, how the value lists are supplied (single delimited string vs repeated argument), and what the result looks like.

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% across four parameters, so the description must compensate. It only loosely maps 'text' and 'suffixes or values', leaving the duplicate pairs ambiguous: it never explains how 'input' differs from 'text', or how 'values' differs from 'suffixes', nor which (if any) are required.

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?

States a concrete verb and resource ('Checks whether text ends with any of the given suffixes or values'), so an agent knows it is a boolean predicate over a string. It does not differentiate itself from near siblings such as x402-contains-any or x402-common-suffix, which the name alone must carry.

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 gives no when-to-use guidance, no prerequisites, and never names an alternative tool. An agent must infer from the name alone that this is the 'any-of' variant versus a single-suffix or substring check.

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