kingdee_query_instant_cost_compare

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the agent knows it's a safe read. The description adds that it queries a specific table and returns a JSON list, plus provides examples of useful field keys. No contradictions. It goes beyond annotations by detailing the data content.

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 concise (4 lines) and front-loaded with the main purpose, followed by examples. It avoids unnecessary fluff. Could be slightly more structured with bullet points, but overall effective.

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?

Given the tool's complexity (multiple parameters), annotations (read-only), and existence of an output schema, the description covers the main purpose, provides concrete usage examples, and specifies the return format. It does not explain pagination or field meanings in detail, but is adequate for a query tool.

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%, meaning parameter descriptions are generic. The description compensates by giving specific examples for filter_string (material/warehouse) and field_keys, which add meaning beyond the generic schema. However, it does not describe parameters like order_string, start_row, or limit, leaving them to generic descriptions.

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 it queries the 'STK_InstantCostCompare' table and compares instant cost with accounting cost. The verb '查询' (query) and resource are specific. Among siblings, this tool is distinct as it targets a specific cost comparison table, differentiating it from other cost-related query tools.

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 concrete examples of filter_string and field_keys, showing how to filter by material and warehouse. However, it does not explicitly state when to use this tool over other cost-related siblings like query_cost_calculation or query_material_cost, nor does it provide when-not-to-use guidance.

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