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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), and the description adds real context on top: the mechanism is keyword rules rather than AI, output is deterministic per-line, and it is not legal advice. It could go slightly further (e.g. how partial/messy input is handled), but this is solid added value.

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 instruction to paste the text is front-loaded, followed by scope, output shape, and caveats in dense, low-waste sentences. The middle sentence is long but each clause carries distinct information, so nothing feels 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?

For a single-input tool with no output schema, the description covers input expectation, what gets flagged and why, the shape of the return (per-line flags with reasons, rewrites, a suggested list, a guest note), and its limitations. An agent has everything needed to call it and interpret results.

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 coverage is 100% for the single `text` parameter, and the schema already states 'one task per line'. The description reinforces the input expectation ('Paste...') but adds no new format or syntax detail, so 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 description names a specific verb and resource ('Paste Airbnb checkout instructions... Flags tasks that go past Airbnb's simple checkout asks') and enumerates the exact task categories it catches. It is instantly distinguishable from the unrelated sibling tools (claim_deadlines, price_match, vrbo_reprice).

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?

It gives clear usage context ('Paste Airbnb checkout instructions') and scope boundaries ('keyword rules, not AI', 'Not legal advice'), which tells the agent what the tool is for. There are no competing sibling tools to route against, so the absence of explicit when-not guidance is a minor gap rather than a real one.

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