kingdee_query_cost_adjustments

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

Annotations indicate readOnly, non-destructive, idempotent. Description adds context (entity type, typical filters) but does not elaborate on behavior beyond annotations, which already set expectations of safe read operations.

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 very concise, with no wasted words. It front-loads the core purpose and uses a structured code block for examples, making it easy to parse.

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 output schema existence, the description is largely complete for a simple query tool. It could mention pagination or result format more explicitly, but it adequately covers the main purpose.

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?

Input schema already provides descriptions for all parameters. The description adds value by suggesting common filter_string values and recommended field_keys, going beyond schema to guide effective use.

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 cost adjustment orders (STK_CostAdjust). The name and description are specific and align, distinguishing it from sibling query tools for other entities.

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 examples of filter_string and recommended field_keys, aiding effective usage. However, it lacks explicit guidance on when to use this tool versus alternatives like kingdee_query_bills or other cost-related queries.

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