query_spot

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

The description discloses that output is written to a CSV file at file_path, and notes that sy daily fetching is slow. However, without annotations, it does not mention any other side effects or potential errors, leaving some behavioral transparency gap.

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 a single run-on sentence mixing English and Chinese, making it less clear. It could be organized into separate points for each kind, but currently it is somewhat cluttered.

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 provides enough context to use the tool: it explains the two kinds, required parameters, output format, and performance caveats. It even gives examples of valid symbols, which helps an agent construct correct queries.

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?

The schema already has detailed descriptions for each parameter, including required conditions for each kind. The main description adds context about the two query modes and the 10-year depth for sge, but this information is mostly redundant with 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?

The description clearly states 'Query spot prices' and details two kinds (sge and sy) with specific examples. It distinguishes the tool as a spot-price query, which helps an agent identify its purpose among sibling tools, though it does not explicitly name alternatives.

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 provides usage guidance by specifying which parameters are required for each kind: symbol for sge, symbols and dates for sy. It also notes that sy fetching is slow and limited to 1-year ranges, which informs decision-making.

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