List Purchase Contracts

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint as true. The description adds value by specifying support for OData $filter/$top/$skip/$select, which informs the agent about pagination and filtering capabilities, and clarifies that only headers are listed (not line items).

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 extremely concise: two sentences that front-load the purpose immediately. No redundant or extraneous information, every word 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?

While annotations cover safety, the description lacks details on return format (e.g., fields returned) and default behavior (e.g., maximum items, ordering). Given no output schema, the description could be more complete to help an agent understand what the response contains.

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?

With only 25% schema description coverage (only filter has a description), the description mentions support for $filter/$top/$skip/$select but does not explain the semantics of top, skip, or select beyond schema constraints. It adds some context but insufficient to compensate for the low coverage.

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 contract (outline agreement) headers', specifying the verb (list), resource (purchase contract headers), and scope (headers only), which distinguishes it from siblings like s4_purchase_order_list or s4_purchase_contract_get.

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 contract headers but does not provide explicit guidance on when to use this tool versus alternatives (e.g., get for detailed view, purchase order list for orders). No exclusions or context are mentioned.

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