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

Annotations already establish that this is a read-only, non-destructive lookup, so the description does not need to repeat the safety profile. It adds useful context by listing returned attributes and noting prefix matching, though it does not explain no-match or multiple-match behavior for prefix lookups.

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 definition is compact and front-loaded: the core lookup behavior, identifier options, returned fields, and endpoint are all packed into one efficient sentence.

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 simple read-only lookup with full schema coverage and annotations, the description is mostly complete, especially since it lists return fields in the absence of an output schema. The main missing context is how this tool differs from the very similar vintrace_get_stock_item sibling.

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 parameter meanings are already clear from the schema. The description adds the one-of invocation pattern ('Give code or id'), but it does not clarify whether both may be supplied or which takes precedence.

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 states a specific verb and resource: find one stock item by code prefix or id, and lists the fields it returns. It is clear on its own, but it does not distinguish itself from the sibling vintrace_get_stock_item, which appears to cover the same resource.

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 phrase 'Give code or id' implies how to invoke it, and the code-prefix behavior is noted. However, there is no guidance on when to use this versus vintrace_get_stock_item, vintrace_search_items, or vintrace_list_inventory.

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