List Sales Contracts

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description is not burdened with repeating those. It adds transparency by specifying that only headers (not full contracts) are returned, and that standard OData operations are supported. The behavior is clear and non-contradictory.

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 with two sentences. The first sentence clearly states the primary purpose, and the second lists the supported OData parameters. Every word adds value; no redundancy.

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 no output schema, the description is fairly complete. It identifies the resource (headers), supported features (OData), and with annotations indicating read-only and idempotent behavior. Missing details like default pagination or result format are acceptable given the concise style.

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 only 25% (only 'filter' has a description). The description compensates by grouping parameters as standard OData operations, implying their typical semantics. However, it does not explain each parameter individually beyond the schema's limited 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 it lists sales contract headers, which distinguishes it from sibling tools like s4_sales_contract_get (single) and s4_purchase_contract_list (purchase side). The verb 'List' and resource 'sales contract headers' are specific and unambiguous.

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 mentions support for OData parameters ($filter, $top, $skip, $select), which guides on how to use the tool. However, it lacks explicit guidance on when to use this vs other list tools (e.g., s4_sales_order_list) and does not provide usage exclusions.

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