list_merchants

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

The description includes the API endpoint and return structure beyond the input schema, disclosing the response includes 'total' and 'merchants[]' with fields. No annotations are provided, so the description compensates with behavioral details.

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 well-structured with sections like 【用途】, 【呼叫的 Shopline API】, 【回傳結構】, and is concise with no unnecessary 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?

For a tool with no parameters and no output schema, the description fully compensates by explaining purpose, API endpoint, and response structure, making it complete.

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 tool has zero parameters and schema coverage is 100%, so baseline is 4. The description adds value by detailing the response structure, which is not present in the 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 '取得所有商家清單' (list all merchants) and explains it is for viewing accessible merchant accounts, distinguishing it from sibling 'get_merchant_detail' which retrieves a single merchant.

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 provides explicit usage context: '適合多商家環境下確認可操作的商家範圍' (suitable for multi-merchant environment to confirm operable scope). It does not explicitly mention when not to use or alternatives, but the context is clear.

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