kingdee_query_production_pick_materials

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds minimal value beyond stating it returns a JSON list and explaining filter_string syntax. No additional behavioral traits (e.g., permissions, side effects) are disclosed.

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 front-loaded with the main purpose and includes helpful code-like examples. It is reasonably concise, though the list of filter_string examples and field_keys could be more compact.

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 annotations and schema, the description is adequate for a basic query tool. It specifies the form ID and return format, but does not mention pagination defaults (e.g., limit=20) or that filter_string and field_keys are optional, though the schema covers these.

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 covers all parameters with descriptions, so baseline is 3. The tool description adds examples for filter_string and recommended field_keys, but does not explain other parameters like order_string, start_row, or limit beyond what the schema provides.

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 the tool queries production pick materials (PRD_PickMtrl) list, providing examples of filter_string and recommended field_keys. It is distinct from sibling query tools like kingdee_query_bills or kingdee_query_production_orders.

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 for common scenarios (approved, specific order, specific warehouse) and recommends field_keys, but does not explicitly state when to use this tool versus alternatives or provide exclusion criteria.

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