kingdee_query_production_orders

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds value by specifying the return format (JSON string) and providing filter examples, but it omits details on pagination, limits, and error behavior.

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: one purpose line, bulleted examples, and return type. It is well-structured and front-loaded with key information, though it could be more organized by explicitly mapping parameters to examples.

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 simplicity, the description covers purpose, filter examples, and recommended fields. However, it fails to resolve the ambiguity of the form_id parameter (whether fixed or user-supplied) and does not detail the return JSON structure, leaving gaps for a comprehensive understanding.

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% for the top-level 'params' parameter, but the schema itself includes descriptions for nested properties. The description adds example values for filter_string and field_keys, partially compensating, yet it does not explain parameters like form_id, order_string, start_row, or limit.

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 production order (PRD_MO) list, with specific verb '查询' and resource '生产订单'. It provides common filter strings and recommended fields, distinguishing it from generic query tools like kingdee_query_bills by specifying the form type PRD_MO.

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 offers practical filter and field key examples, aiding effective use, but lacks explicit guidance on when to use this tool versus siblings (e.g., kingdee_query_bills) and does not clarify whether the form_id parameter should be set to PRD_MO or is hardcoded.

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