kingdee_query_asset_transfer

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds no new behavioral traits beyond the context of querying asset transfers. It does not disclose pagination behavior or other operational details not covered by 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?

Extremely concise: two short paragraphs with bulleted examples. Every sentence earns its place, and the key information is front-loaded. No wasted words.

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 presence of an output schema and standard query pattern, the description is largely complete. It covers purpose, key parameters with examples, and entity meaning. Minor gap: no mention of pagination limits or default ordering, which are in the schema but not highlighted.

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?

Although schema description coverage is 0% per signal, the description provides concrete examples for filter_string and field_keys, adding value beyond the generic schema descriptions. This helps agents craft effective queries, though it does not cover all parameters like order_string or pagination.

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?

Clearly states '查询资产调拨单' (query asset transfer orders) and identifies the resource as 'FA_Transfer'. Explains the nature of asset transfers, distinguishing it from sibling tools that query other asset-related records like asset cards or fixed assets.

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?

Provides practical examples of filter_string and recommended field_keys, aiding usage. However, it does not explicitly state when to use this tool versus alternatives like kingdee_query_asset_card or kingdee_query_fixed_asset, nor does it mention when not to use it.

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