kingdee_query_mrp_result

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so description's addition of downstream implications is helpful but not critical. No mention of rate limits, auth, or side effects.

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 with three clear sentences, each serving a distinct purpose: resource identification, business context, and return format. 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?

For a read-only query tool with annotations and output schema mentioned, the description covers the data's origin, structure, and use. Minor lack of pagination or error details but not critical given low 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?

Even though schema properties have descriptions, the context signals indicate 0% coverage, meaning the description must compensate. However, the description adds no parameter-level guidance beyond what is in the schema, leaving a gap.

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?

Description clearly states verb '查询' and resource 'MRP运算结果', providing business context of origin and downstream use. However, it does not explicitly differentiate from similar query tools like kingdee_query_production_plan.

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?

Implied usage context (MRP results from various demand sources) but no explicit when-to-use or when-not-to-use guidance, nor alternatives among many sibling query tools.

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