kingdee_view_production_order

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

Annotations already declare read-only and idempotent. Description adds required form_id value and alternative bill_no parameter. No contradictions, but doesn't elaborate on behavior beyond safety profile.

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?

Short and to the point, listing required parameters and return type. Could be better structured but front-loads key info without excess.

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?

Adequate for a simple view tool with output schema. Missing explanation of 'mode' parameter and more detailed return structure, but not critical.

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?

Adds meaning beyond schema: specifies that form_id must be 'PRD_MO' and that bill_id can be either FID or bill_no. Schema already describes parameters, but description clarifies usage constraints.

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?

Describes viewing complete details of a production order with specific verb and resource. Distinguishes from sibling query tools by emphasizing full details, though not explicitly differentiating from other view tools.

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?

States required parameters and return type, implying use when needing full details of a specific order. Lacks explicit when-to-use or alternatives, but context with siblings helps differentiation.

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