coupon_template_list

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

No annotations provided, so description carries full burden. It only repeats schema info about country parameter. No disclosure of return format, pagination behavior, idempotency, or side effects (e.g., read-only).

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?

Very concise single sentence with no fluff, but at the cost of missing critical information. Adequate for conciseness but lacks necessary detail.

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 6 parameters, no output schema, low schema coverage, and sibling tools, the description is incomplete. It does not explain filtering, ordering, default behavior, or the effect of omitting the country 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?

Schema description coverage is only 17% (only 'country' has a description). The description adds no meaning beyond the schema for the other 5 parameters (pageNum, pageSize, couponName, templateNo, templateName), failing to compensate for the low coverage.

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?

Description clearly states 'List coupon templates' as verb+resource, but does not distinguish from sibling 'coupon_template_get' which likely retrieves a single template. Missing mention of pagination parameters (pageNum, pageSize) which are part of the function.

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?

No guidance on when to use this tool vs alternatives like 'coupon_template_get'. No exclusions or prerequisites mentioned. The 'supports country header' hint is basic and does not help in decision-making.

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