POS Rescue

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

The description adds meaningful behavioral context: it discloses the tool is a diagnostic/consultative service (not a direct action), notes the pricing ('5 MESH/call'), and hints it's part of the broader tool-a-commerce ecosystem. With annotations declaring readOnlyHint=false and openWorldHint=true, the description complements rather than contradicts them. It doesn't detail failure modes or edge cases but is appropriate for a diagnostic tool.

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 a single, dense paragraph that front-loads the value proposition and enumerates outputs in a compact list. No wasted words—every phrase contributes (the vendor list, the deliverables, the pricing, the workaround angle).

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 3-field nested payload with 100% schema coverage and no output schema, the description sufficiently sets expectations: it frames what problems it solves, what deliverables it produces, and the ecosystem context. The workaround mention ties it to related tools. It could name sibling tools explicitly, but is otherwise complete for its complexity.

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%, so the schema already documents both 'pos' and 'trouble' parameters, including the 'pos' format hints and the exclusivity enum semantics with its 'fails closed' note. The description adds the workflow context (what you get back) but adds no parameter-specific detail beyond the schema; baseline 3 is correct.

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 clearly states the tool's purpose: helping users stuck on POS integrations (Toast, Square, Clover, Micros) get a diagnosis, step-by-step plan, and workflow applicability. It names specific resources and a distinct output ('diagnosis, plan, workaround check') that distinguishes it from sibling tools like direct-checkout or install-matrix.

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 tells users when to use it ('stuck on a POS integration') and what to provide ('describe the trouble'). It also signals the diagnostic-plan-workaround output. However, it doesn't explicitly exclude alternatives or name direct-checkout as the sibling to pick for the actual checkout path, though 'whether the owner-direct checkout workaround applies' implies that relationship.

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