push_bill

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

With no annotations, the description carries the full burden. It only lists parameters and examples, but does not disclose side effects, prerequisites, error behavior, or whether the operation is irreversible. 'Push' implies creating a downstream document, but no details are provided.

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 a well-structured docstring with a short purpose line and an Args list. Each parameter is one line, making it easy to scan. Slightly verbose but not excessive; it earns its place.

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?

The description covers all 9 parameters effectively, and an output schema exists so return values are not needed. However, it lacks usage context and behavioral side effects (e.g., what happens on error, whether it creates a new document or updates). Given the tool's complexity, more context is needed for full completeness.

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?

The schema has no parameter descriptions (coverage 0%), but the description thoroughly explains every parameter, including examples (form_id: SAL_SaleOrder), relationships (numbers and ids are mutually exclusive), and JSON formatting for custom_params. This fully compensates for the schema 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?

The description clearly states the tool pushes Kingdee Cloud Star documents (e.g., sales order to delivery notice), with a specific verb and resource. This distinguishes it from sibling tools like query_bill or save_bill.

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?

No explicit guidance on when to use this tool versus alternatives. The description only explains parameters like '不填则用默认规则' (use default rule if not filled) but does not mention when to prefer this over related operations such as save_bill or execute_operation.

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