Create Sales Contract

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

Annotations already declare destructiveHint=true and readOnlyHint=false, indicating mutation. The description adds that at least one item is required, which is useful but doesn't disclose additional behavioral traits (e.g., side effects, authorization needs, rate limits).

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?

Single concise sentence with no wasted words. Every element serves a purpose: action, constraints, required fields.

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 core creation logic and constraints. No output schema is provided, so more detail on return value or potential errors would improve completeness, but the description is already strong for a create 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 description coverage is 100%, so parameters are fully documented. The description lists required fields but adds no semantic meaning beyond what the schema provides. Baseline score of 3 is appropriate.

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 'Create a sales contract' and specifies required header and item fields. It distinguishes from sibling tools like s4_sales_contract_update, s4_sales_contract_list, s4_sales_contract_get, and other S4 document tools by focusing on creation.

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 explicitly says 'the header cannot be created without at least one item/association' and lists required fields, providing clear context. However, it does not explicitly state when to use this tool vs. alternatives like s4_sales_order_create or s4_sales_contract_update.

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