get_merchants

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

With no annotations, the description carries the full transparency burden. It discloses the data source ('Derived from app events'), the default status behavior, and the return structure (JSON string with keys). It does not explicitly state read-only or permissions, but it is a list operation and the description is informative enough for a safe read.

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 efficiently structured with Args and Returns sections, no filler, and each sentence adds value. It packs necessary details into a clear, scannable format.

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 two-parameter list tool with an output schema, the description covers purpose, parameter semantics, data origin, and return shape. It is complete for selection and invocation without redundancy.

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 0%, but the description fully compensates by explaining app_id as 'App GID or numeric ID (required)' and status with exact allowed values and default. This is exactly the needed guidance beyond the bare schema.

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 a specific verb and resource: 'List merchants (stores) using a specific app.' This distinguishes the tool from siblings like get_merchant_lookup or get_churned_merchants by emphasizing the app-scoped, list-oriented nature.

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?

Parameter usage is well explained with status options and default, but there is no explicit when-to-use versus alternatives. The 'Derived from app events' note gives some context, but the description does not reference sibling tools like get_churned_merchants or edge cases.

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