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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the filtering capability but doesn't elaborate on pagination behavior (which is covered in the schema) or any limits. With annotations covering the core behavior, a 3 is appropriate.

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 description is two short sentences, front-loaded with the main purpose and then the filtering options. It is efficient and contains no unnecessary words, though it could be slightly more informative.

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?

Given the tool's simplicity (4 optional parameters, no nested objects, no output schema), the description coupled with annotations and the detailed schema is sufficient for an agent to invoke it correctly. It could benefit from mentioning pagination defaults, but those are already in the schema.

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 schema fully documents all parameters (page, part_id, per_page, feature_id) including their formats and constraints. The description only mentions filtering by feature or part, which is already in the schema. Baseline 3 when 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?

The description states a specific verb (List) and resource (parts associated with infrastructure features), and it distinguishes itself from other 'list_*' tools by clarifying the relationship to infrastructure features. It's clear enough that an agent would know this retrieves parts linked to infrastructure assets, not standalone parts.

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 description says 'Filter by feature or part' which implies usage, but it does not explicitly state when to use this tool vs alternatives like list_parts or list_infrastructure_assets. No exclusions or prerequisites are provided.

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