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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds nothing behavioral — no note on error behavior for a missing kit_id, no indication of what is returned, no scope constraints. It does not contradict the annotations.

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?

Four words that read as a label rather than a description, with no front-loaded verb or purpose. This is under-specification rather than effective conciseness — the sentence is short because it omits necessary information.

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?

No output schema exists, so the description should at least signal what a 'kit piece' lookup returns (a piece object with outfit/place/prop attributes). For a simple read tool with full annotation coverage and full param coverage, this is the main remaining gap, and it is unfilled.

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?

Single parameter with 100% schema description coverage, so the schema already documents 'The kit piece id'. The description adds no further semantics about the id format or where it comes from; baseline 3 applies when the schema does the work.

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 name carries the verb+resource (get a kit piece), and the fragment 'One outfit, place or prop' clarifies what a kit piece conceptually is. But the description itself does not state that it retrieves a single kit piece by id, nor distinguish it from list_kit or get_look. Purpose is only implied, not stated.

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?

No indication of when to use this versus list_kit (browse all pieces) or get_look (which presumably composes pieces). The agent must infer that kit_id is obtained elsewhere and that this is the single-item lookup path.

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