decode-merchant

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

With no annotations provided, the description fully discloses behavior: read-only, no signing or paying, and details the output shape including the autonomous payment verdict. It's transparent about what the tool does and does not do.

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 two sentences: first explains the core function and output, second clarifies read-only nature and points to alternatives. Every sentence is essential, front-loaded with key information, and no wasted words.

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?

Given no output schema, the description details the return shape sufficiently. It also positions the tool within the larger kit by referencing wallet lessons for payment. The description is complete for a read-only tool with one parameter.

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?

The only parameter 'url' is fully described in the schema. The description adds context about the type of URL (product URL on open web) but does not add new semantic constraints beyond the schema. Since schema coverage is 100%, baseline of 3 is appropriate.

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 reads any product URL and returns a structured shape with specific fields (what, who, cost, stock, verdict). It uses a specific verb ('read') and resource ('product URL on the open web'), and the purpose is distinct from sibling tools which mostly deal with wallets and payments.

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 explicitly states it reads only, never signs or pays, and provides guidance on when to use alternative tools ('To pay an autonomous result, use this kit's wallet lessons'). This gives clear context for usage and exclusions.

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