save_parts

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

No annotations are provided, so the description carries the full disclosure burden for a mutation tool. It never states whether omitted fields are preserved or nulled on update, whether the batch is transactional or partially applied on failure, or what permissions are required. 'Batch' is the only behavioral signal given.

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?

Front-loaded with the core action in the first sentence, and the Args block is short. The field examples and 'part_type' note are somewhat redundant with the nested schema, keeping it just short of maximally efficient.

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?

An output schema exists, so return values need no explanation. However, for a batch upsert with no annotations, the description should say how create vs. update is determined and how the batch behaves on partial failure; those gaps leave the agent guessing about mutation semantics.

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 top-level schema exposes only 'parts' with no description, but the nested PartSaveInput definition documents every field in detail, so the agent is not actually left in the dark. The description's Args block largely repeats what the nested schema already says ('part_number' required, 'part_type' accepting an ID or category path) rather than adding new meaning.

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?

States a specific verb+resource with scope: 'Batch create or update parts'. Cleanly distinguishes from save_part_types (types, not part records) and get_parts/list_parts. It stops short of naming a sibling or the create-vs-update selection condition, so it is clear but not differentiating.

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?

Usage is only implied by the phrase 'Batch create or update', leaving the agent to infer that passing 'part_id' selects an update while omitting it creates. No guidance about when to prefer this over save_part_types, delete_parts, or manage_bom_parts, and no prerequisites or batch-size limits.

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