industry_daily_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool queries local SQLite data, implying a read operation, but does not disclose default behavior, data freshness, whether the database must be pre-populated, or how date and industry filters behave.

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 short sentence with no redundancy, but it is under-specified rather than usefully concise. It omits all parameter and usage information that the agent needs, so the brevity does not serve the tool's usability.

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?

An output schema exists, so return-value documentation is less critical, but the description still lacks parameter semantics, usage guidance, and any behavioral context. For a tool with four optional parameters and no annotations, this is insufficient for an agent to select and invoke it reliably.

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 0%, and the description does not explain any of the four parameters: limit, end_date, industry, and start_date. The agent has no way to know the expected date format, how industry should be specified, or what default limit=20 implies. The description fails to compensate for the undocumented 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 '查询本地 SQLite 中的行业日行情' clearly identifies the action (query), the resource (industry daily market data), and the storage location (local SQLite). It is specific enough to distinguish it from collection-oriented siblings like industry_daily_collect, though it does not explicitly differentiate from similar query tools like industry_quotes or industry_sw_daily.

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 no guidance on when to use this tool versus its many siblings, such as industry_quotes, industry_sw_daily, or industry_daily_collect. There are no conditions, exclusions, or alternative recommendations, leaving the agent to infer usage context from the name alone.

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