List Purchase Requisitions

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

Depiction of OData support ($filter/$top/$skip/$select) adds behavioral detail beyond annotations (readOnlyHint, openWorldHint, idempotentHint). Does not go into pagination limits or default ordering, but sufficient for basic API usage.

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?

Two sentences, no wasted words. Purpose stated first, supported features second. Highly efficient.

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?

No output schema is provided, and description does not mention return format or fields. For a list tool, agents need to know what data they receive. Lacks 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?

Schema coverage is low (25%) and description only mentions OData parameters generically. Does not explain each parameter's purpose or constraints beyond what the schema provides for 'filter'.

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?

Description clearly states action (List) and resource (purchase requisition headers). Distinguishes from sibling tools like get/create/update by specifying list operation and 'headers' scope.

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 vs alternatives like s4_purchase_requisition_get (if a single document is needed). Does not mention search or filtering alternatives.

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