kingdee_query_purchase_order_progress

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

Adds significant behavioral context beyond annotations: return format (JSON), demo-verified fields, conditional field presence, and business close rules. No contradiction with 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?

Description is lengthy but well-structured with bullet points and sections. Some redundancy (e.g., listing all fields might be omitted). Could be more concise.

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?

With annotations providing safety info and output schema implied, the description covers return fields, conditional behavior, and business rules. It is sufficiently complete for an AI agent to understand the tool's output and constraints.

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 coverage is 0%, but the description only mentions the default for filter_string. Does not explain start_row or limit parameters. The description adds minimal value over the schema for parameter understanding.

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?

Clearly states it queries purchase order line details and execution progress, distinguishing from sibling tool kingdee_query_purchase_orders by specifying line-level fields. The verb 'query' and resource 'purchase order progress' are specific.

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?

Explicitly contrasts with a sibling tool, notes default filter for audited documents, and explains field availability depends on supply chain module. Does not state when not to use, but provides adequate context.

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