iqms_purchase_orders_list

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it lists and filters, but does not mention pagination (the limit parameter is not referenced), ordering, authentication requirements, or what data is returned. Essential behavioral context is missing.

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 highly concise: two sentences with no wasted words. The action is front-loaded, and the filtering options are listed efficiently.

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?

Without an output schema, the description should explain what the tool returns (e.g., fields, format). It does not address this. Additionally, the limit parameter is omitted from the description, and there is no mention of default behavior or ordering. The tool is incomplete for an agent to use without risk.

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 description coverage is 40%, with only two parameters having descriptions. The description maps to the main filter parameters (status, supplier_id, expected_before, expected_after) but does not mention the limit parameter. It adds some value by grouping filters but does not compensate for the low coverage fully.

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 'List purchase orders' with a specific verb and resource, and mentions filtering by status, supplier, or expected receipt date, which distinguishes it from siblings like iqms_workorders_list or iqms_sales_orders_list.

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?

The description implies usage for listing purchase orders with filters, but provides no explicit guidance on when to use this tool vs other list tools or alternatives. There is no mention of exclusions or context.

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