get_merchant_hints

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool returns pre_steps and platform notes, implying a read-only lookup, but it does not explicitly state that it has no side effects, nor does it mention permissions or rate limits. The purpose is clear, but some behavioral traits remain undisclosed.

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 consists of three concise, front-loaded sentences. Each sentence adds valuable context: the action and input format, the expected output, and the recommended usage timing. No waste or redundancy.

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 simple single-parameter tool with no output schema, the description adequately covers what the tool does, the input format (including the platform key variant), what it returns, and when to use it. This is sufficient for an agent to invoke it correctly in the broader checkout flow.

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 input schema already describes the 'domain' parameter with examples (100% coverage), but the description adds an alternative accepted format: a platform key like '_platform_etsy'. This information is not present in the schema, meaningfully extending the parameter documentation.

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 uses the specific verb 'Get', identifies the resource as 'merchant navigation flow', and highlights the distinction from sibling payment-transaction tools by positioning it as a pre-checkout navigation lookup. It clearly states the tool's scope and purpose.

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 'Call BEFORE starting checkout to understand the multi-step flow', providing clear context for when to use the tool. It does not explicitly mention alternative tools, but the sibling tools are clearly different operations, so the guidance is sufficient.

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