List Purchase Orders

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, indicating a safe read operation. The description adds value by specifying OData $filter/$top/$skip/$select support, which clarifies how the listing can be customized beyond the schema.

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 two sentences long, front-loading the purpose and adding essential OData support context. No superfluous words; every part 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?

For a list tool with four optional parameters and no output schema, the description is adequate. It covers purpose and filtering capabilities. However, it could be more complete by mentioning that the output is a list of purchase order headers and perhaps the default field selection.

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 low (25%), with only 'filter' having a description. The description mentions 'OData $filter/$top/$skip/$select', providing context that the parameters follow OData syntax, but it does not elaborate on each parameter's purpose or constraints beyond the schema names.

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 order headers' with a specific verb and resource. It distinguishes itself from sibling tools like s4_purchase_order_get (single record retrieval) by focusing on listing, and mentions OData support for further specificity.

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 but does not explicitly state when to use this tool over siblings like s4_purchase_order_get or s4_purchase_order_create. No when-not-to-use or alternative guidance is given, leaving the agent to infer context from the sibling list.

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