kingdee_save_bill

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

Annotations are minimal (readOnlyHint=false, etc.). Description adds significant behavioral context: auto-correction of typos, FID handling, and is_delete_entry behavior. This adds value 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?

Very concise: two paragraphs (rules and example) with clear bullet points. Every sentence earns its place. Front-loaded with purpose and rules.

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 tool's complexity (create vs. update, auto-correction, 4 parameters) and presence of output schema, the description covers all key aspects and provides a complete usage example.

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 has descriptions for all parameters, but description adds a concrete purchase order model example and clarifies the relationship between FID and is_delete_entry. This supplements the schema well.

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 it creates or modifies Kingdee documents (e.g., purchase orders, sales orders) with specific verb+resource. It distinguishes from sibling tools like kingdee_audit_bills or kingdee_query_bills.

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 clear rules: new need no FID, modify must have FID and set is_delete_entry=false. Also mentions auto-correction of field names. Could explicitly mention when not to use (e.g., for asset or production order specific saves) but overall helpful.

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