search_promotions

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

Discloses the API endpoint and return structure, which is useful. However, no annotations exist, so the description should also mention that this is a read-only operation or require any permissions, but it doesn't.

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?

Well-structured with sections, front-loading the purpose. Each sentence adds value, though it could be slightly shorter without losing clarity.

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, it adequately describes the return structure and fields. It also explains integration with get_promotion_detail. However, it lacks information on pagination or error responses.

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 coverage is 100%, and the description adds marginal value beyond the schema. It re-iterates keyword and max_results but does not explain how they affect search behavior (e.g., partial match) beyond 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?

Clearly states it searches promotions by keyword, with examples like '週年慶'. Although it differentiates from get_promotion_detail by noting results include IDs for that call, it could explicitly distinguish from list_promotions.

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?

Provides context for when to use (finding specific promotions by name) and mentions get_promotion_detail as next step, but does not explicitly say when not to use or provide alternatives like list_promotions.

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