kingdee_query_misc_movement_detail

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description adds no contradictions. It adds that the return is a JSON-formatted list, which is useful but not critical beyond annotations.

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 well-structured with sections for purpose, examples, and recommended fields. It is somewhat verbose due to the code block but remains clear and informative. No unnecessary repetition.

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?

For a query tool with pagination and filtering, the description covers the core usage with examples. It does not detail the output schema (though one exists) or explain pagination parameters, but the schema provides defaults. Overall, it is reasonably complete given the complexity.

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 parameter, but nested property descriptions exist in the schema. The description adds value by giving concrete filter_string and field_keys examples. However, it does not explain the required form_id parameter (which should likely be set to 'STK_MiscMovementDetail' based on the table name), potentially causing confusion.

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 the miscellaneous movement detail table (STK_MiscMovementDetail) for viewing inbound/outbound details. It uses a specific verb '查询' (query) and resource, distinguishing it from sibling query tools like kingdee_query_bills or kingdee_query_inventory.

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 filter_string examples and recommended field_keys, helping the agent construct queries. However, it does not explicitly state when to use this tool vs. other query tools (e.g., for general bills vs. misc movement), though the table name makes it clear.

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