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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety and determinism profile is covered. The description adds the concrete format families it recognizes, but is silent on behavior for unrecognized or malformed input (error vs. pass-through) and on output shape, which are the meaningful remaining unknowns.

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?

Three short sentences, front-loaded with the verb and resource, followed by supported formats and rationale. No filler or repetition.

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 single-parameter, non-destructive, idempotent transformation with no output schema, the description covers purpose, scope of formats, and motivation. The only meaningful gap is failure behavior for unrecognized part numbers, which an agent would want to know before calling.

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?

Only one parameter and schema description coverage is 100%, so the baseline is 3. The vendor format examples in the description indirectly illustrate what the partNumber string may look like, but add no syntax, casing, or separator rules beyond the schema.

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 ('Normalize an IT hardware part number into its standard form') and scopes it with the vendor formats handled (HPE, Dell, IBM/Lenovo). It does not explicitly name or contrast with the close sibling validate-pn, so it falls short of full sibling differentiation, but the intent is unmistakable.

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?

'Critical for deduplication and accurate lookups' implies when to reach for it, but there is no explicit when-to-use/when-not guidance and no named alternative (e.g., validate-pn for checking validity without transforming). Usage must be inferred.

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