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

No annotations are provided, so the description carries the full burden. It says '即時查詢' (real-time query) but discloses nothing about data source, freshness/refresh cadence, caching, or error behavior for non-existent periods. For a read-only lookup this is thin, though low risk.

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?

A single front-loaded sentence covering the resource, the games, and the returned fields, with zero filler. Efficient and easy to scan.

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 lookup with no output schema, the description covers what is fetched but not the shape of the response (e.g., per-game prize tiers) or the behavior when a period is missing. Adequate but leaves the return contract implicit.

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 50%: the period parameter is self-documented with its default ('不填為最新'), and the game enum values are self-explanatory. The description names the three games in Chinese but adds no mapping to enum values or format details, so it does not materially exceed 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?

States a specific verb+resource ('取得...開獎號碼與各獎項獎金') and names the three lottery games covered, so the agent knows what data comes back. However it does not distinguish itself from the sibling life__check_lottery, which reads as the same domain and could easily be confused with it.

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?

There is no when-to-use, when-not-to-use, or alternative guidance. The presence of a near-identical sibling (life__check_lottery) makes the absence of routing guidance a real gap, since the agent has no signal for choosing between them.

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