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 does disclose the response shape (matched count, prize, per-ticket prize, redemption deadline), which is useful since there is no output schema, but it omits constraints such as which games require the 'second' zone or whether a draw period must already be released.

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 compact sentence, front-loaded with the category tag and the input/output contract. Nothing is wasted, though the bracketed tag adds little information value.

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 4-param tool with no annotations and no output schema, describing the return values is a genuine plus, but the undocumented 'period' parameter and the absent routing to life__get_lottery_results leave it only partially 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?

Schema description coverage is only 25% (only 'second' is documented), so the description must compensate. It names 'game' and 'numbers' but says nothing about 'period' (the draw cycle) – that parameter is undocumented in both the schema and the description, leaving a real gap for a 4-param tool.

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 (對彩券/check) and resource (lottery), and even enumerates the return values (matched count, prize tier, per-ticket prize, redemption deadline). It is clear what the tool does, but it never distinguishes itself from the sibling life__get_lottery_results, which likely serves the winning-numbers lookup.

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?

Usage is only implied by 'input game and numbers' – the agent can infer this is for checking a user's own ticket, but there is no explicit when-to-use, no prerequisite, and no mention of the sibling life__get_lottery_results as the alternative for fetching drawn numbers.

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