Create Complex Company Item

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

The description discloses that the tool creates an item, which is consistent with annotations (readOnlyHint=false). However, it does not add behavioral context beyond what annotations imply, such as required permissions, side effects (e.g., database write), or limits (e.g., SKU uniqueness). Annotations already hint at mutability and non-destructiveness, so the description adds minimal extra value.

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 very concise: one sentence stating the purpose and a bullet-like Args section. It front-loads the main action and uses minimal words, earning its place without fluff.

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 basics of what the tool does and its two parameters, but lacks important context like return value (no output schema), error conditions, prerequisites (e.g., company must exist), or behavior on duplicate SKU. For a creation tool with a nested object, more detail would be beneficial, but the description is minimally adequate.

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 the baseline is 3. The description repeats parameter details from the schema but adds slight context: for companyId, 'to create item under' and for item, lists example fields like 'sku, description, weight, dimensions'. This adds value beyond the schema, but not extensively.

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 title and description clearly state the tool creates a 'complex item (product/SKU with detailed packaging info)' for a company. The verb 'creates' and resource 'complex item' are specific, and it distinguishes from sibling tools like 'get_item_complex' and 'delete_item'.

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 no guidance on when to use this tool versus alternatives such as 'machship_create_consignment_with_complex_items' or 'machship_get_item_complex'. There is no mention of prerequisites or conditions that favor this tool over others.

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