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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the write semantics and safety profile are covered structurally. The description adds a genuinely useful piece of context, the required parts:write scope, which is not in the annotations. It says nothing about duplicate handling, idempotency, or what the response contains.

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 short sentences, zero filler, and the core operation is front-loaded ahead of the scope prerequisite. Nothing is wasted.

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?

For a 12-parameter mutation, the description is thin, but the fully documented schema and the explicit safety annotations carry most of the burden. The remaining gap is the absence of any return-value or duplicate-handling information, which matters somewhat for a non-idempotent create.

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% across all 12 parameters, so the schema already documents name, cost, quantity, supplier_id (with its resolution hint), and the rest. The description contributes no additional parameter meaning. Baseline 3 applies when the schema does the heavy lifting.

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 and resource: 'Create a new part/inventory item.' The verb clearly separates it from get_part, update_part, list_parts, and delete_part. However, it does not clarify its boundary against adjacent creation siblings such as create_part_category or create_asset_part.

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 only guidance is a permission prerequisite ('Requires parts:write scope'). It never says when to use this versus bulk_create, create_part_category, or create_asset_part, which are all present in the sibling list. The reader must infer usage from the name alone.

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