Create Purchase Order

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

Annotations already indicate destructiveHint: true and readOnlyHint: false, so the description's 'Create' aligns. It adds context about creating a PurchaseOrderAccountAssignment record for account-assigned items, but does not disclose side effects, authorization needs, or rate limits. The behavioral disclosure is adequate but not thorough.

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 two sentences long, front-loading the core purpose and required fields, then addressing a special case. Every sentence is necessary and no redundant information is present.

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?

Given the complexity (nested objects, account assignment) and lack of output schema, the description fails to mention what the tool returns (e.g., purchase order number or confirmation). It also omits error handling or validation notes. The tool's response is critical for agent workflow, and its absence leaves a significant gap.

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%, so the baseline is 3. The description adds value by explicitly listing required header and item fields, and clarifying the relationship between accountAssignmentCategory and accountAssignment for sales order tie-ins. This goes beyond the schema's individual descriptions.

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 purchase order with at least one item,' identifying the specific verb and resource. It distinguishes itself from sibling tools like s4_purchase_order_list, s4_purchase_order_get, and s4_purchase_order_update 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 implicitly indicates when to use the tool (to create a purchase order) but provides no explicit guidance on when not to use it or how it compares to alternatives like s4_purchase_contract_create or s4_purchase_requisition_create. No context on prerequisites or exclusions is given.

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