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

The description goes beyond the readOnlyHint annotation by explicitly stating it does not create a cart or book anything. It also describes the output structure, including how missing required vs optional fields are handled and the 'dem_kunden_sagen' field, providing rich behavioral context.

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 three sentences and well-structured, with the main purpose first, then usage and output details. It is slightly verbose with some repetition (e.g., 'damit der Kunde' appears twice), but remains focused and clear.

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 tool with 17 optional parameters and no output schema, the description provides sufficient context: the purpose, when to use it, and what the response contains. It could mention error cases or more about edge scenarios, but overall it is complete enough for an agent to use it correctly.

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?

The schema already covers all parameters with descriptions (100% coverage). The tool description adds that all parameters are optional and the AI can query with the current status, which is a useful general semantic note but does not detail individual parameters.

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 the tool's purpose: checking which order details are present and which are missing. It also explicitly differentiates itself from sibling tools like create_cart by noting it does not create a cart or book anything.

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 provides explicit usage guidance: it should be called before create_cart so the customer knows the entire process without opening the website. It also clarifies that all parameters are optional and the tool can be used at any time with the current status.

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