Create Planned Order

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

The description adds significant value beyond annotations by disclosing that the schema may be incomplete and that server-side validation may differ. Annotations already indicate destructiveHint=true and openWorldHint=true, but the description contextualizes the risk of missing mandatory fields, which is critical for an agent invoking the tool.

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: the first succinctly states the action, and the second delivers essential caveat. No unnecessary words; every sentence 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?

The description covers the core function and critical caveat. While it doesn't describe return values (no output schema exists), the agent can infer from the tool type. It could mention the expected result (e.g., created order ID), but overall it's sufficiently complete for an agent to understand and use the tool.

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 coverage is 100% with descriptions for all parameters. The description reinforces that material, mrpPlant, and totalQuantity are practically required, aligning with the schema. It also adds warnings about undocumented mandatory fields, enhancing understanding beyond the raw schema.

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 'Create a planned order' with the title reinforcing the purpose. It names the specific resource (planned order) and action (create), distinguishing it from sibling tools like s4_planned_order_list or s4_planned_order_update.

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 practical guidance by noting that exact mandatory-field rules are not fully documented and advises verification on the tenant. This helps the agent use the tool correctly, though it doesn't explicitly say when to use this tool over alternatives like updating or listing.

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