List Material Documents

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds value by specifying OData filter support, which goes beyond the annotations. No contradictions; well-aligned with read-only nature.

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 concise sentences: first states purpose, second lists supported features. No redundant or extraneous information. Front-loaded and efficiently communicates core functionality.

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; description does not explain return values or pagination behavior. For a list tool, this is a notable gap. However, annotations (idempotent, read-only) and the straightforward purpose partially compensate. Adequate but not fully complete.

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 has 4 parameters with only 25% coverage (only 'filter' has a description). The description explains that the tool supports standard OData parameters ($filter/$top/$skip/$select), adding meaning beyond the bare schema. However, it does not provide detailed guidance for each parameter or examples.

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 the tool lists material document headers (goods movements). It uses a specific verb ('List') and resource ('material document headers'), distinguishing it from sibling tools like s4_material_document_get or s4_material_document_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?

Description implies usage by listing supported OData parameters ($filter/$top/$skip/$select), but does not provide explicit guidance on when to use this tool versus alternatives like s4_material_list or other list tools. No exclusion criteria or prerequisites are mentioned.

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