List Materials (Product Master)

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint. The description adds behavioral context by naming the API source (CE_PRODUCT_0002) and indicating OData support, which helps the agent understand capabilities. No contradiction with annotations.

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 that are efficient and front-loaded: first states the core purpose, second lists supported OData features. No wasted words.

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 reasonably complete: it states the data source and query capabilities. A minor gap is not describing the return format (e.g., a list of product objects), but the name and title imply a list. Given the context, this is adequate.

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 100%, so the baseline is 3. The description reiterates the parameter names ($top, $skip, $filter, $select) as OData features but does not add new meaning beyond what the schema's descriptions already provide (e.g., filter syntax example).

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 materials/products from SAP S/4HANA Cloud and specifies the underlying API (CE_PRODUCT_0002). This differentiates it from sibling tools like s4_material_get (single material) and s4_material_create (create).

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 OData $filter/$top/$skip/$select for focused results, implying usage for list queries with optional filtering/pagination. However, it does not explicitly state when not to use this tool (e.g., for single material retrieval, use s4_material_get) or contrast with other list tools.

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