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

Annotations already declare the safe read-only, idempotent profile, so the bar is low. The description nonetheless discloses useful behavior the annotations cannot: it may return a single likely service, an ambiguous candidate set with verification pointers for Apple/Amazon/Google/Microsoft, or a 'match: purchase' classification for one-off orders.

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 examples are front-loaded and the tool's actual behavior follows immediately, with the chaining hint last. The return-value sentence is somewhat run-on with its stacked 'or... or...' clauses, but nothing is padded.

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, the description carries the burden of describing return values and does so adequately, including the ambiguity case and the purchase classification. The only gap is the slightly mismatched sibling name 'getCancelSteps' versus the actual 'get_cancel_steps', which could briefly confuse a chaining agent.

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 100% and the schema already documents the single 'text' parameter, including its 120-character limit. The description adds no formatting rules or normalization guidance beyond what the schema states, so the baseline 3 applies.

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 opening sentence merely echoes the title, but the body pins down the resource precisely: it maps a raw statement string to the service that generated it. The examples (APPLE.COM/BILL, AMZN Digital, DD *DOORDASH DASHPASS) leave no ambiguity about what input it consumes.

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 quoted example utterances give an agent concrete trigger conditions, and the closing 'Then call getCancelSteps' establishes the downstream workflow. It never states when NOT to use it or contrasts it with siblings like list_services, so it stops short of an explicit routing rule.

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