query_lottery

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

The description indicates a read-only query operation, which is accurate. However, with no annotations provided, it does not disclose any additional behavioral traits such as authentication requirements, rate limits, or data freshness. The description is functional but minimal.

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 extremely concise: one sentence for purpose, then structured Args and Returns sections. Every sentence is necessary and front-loaded with the core purpose. No redundancy.

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?

The description covers input parameters and basic purpose, but lacks details on output format (beyond 'list of results'), error handling, or edge cases. Given no output schema and no annotations, more behavioral context would improve completeness.

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?

Despite 0% schema description coverage, the description's Args section provides meaningful explanations for each parameter: lottery_type options ('double_ball' and 'super_lotto'), and date format (YYYY-MM-DD). This adds value beyond the schema's property titles alone.

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 '查询指定日期范围内的开奖结果' (query lottery results within a specified date range), using a specific verb and resource. It implicitly distinguishes from siblings like get_latest_results (which gets only the latest) and check_prize (which checks a specific ticket).

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 implies usage when needing results for a date range, but does not explicitly exclude scenarios where alternatives like get_latest_results or check_prize might be more suitable. No when-not-to-use guidance is provided.

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