list-rim-bolt-patterns

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

Annotations already provide readOnlyHint and openWorldHint. The description adds the exact bolt pattern format (stud-count × circle-diameter in mm), the optional-filter behavior, and its role as a discovery tool. This provides useful context beyond the annotations without contradictions.

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 sentences, no redundancy. First sentence states function and optional filters; second clarifies format and use case. Every word earns its place.

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 read-only list tool with full schema coverage and helpful annotations, the description covers purpose, value format, and primary use case. It doesn't mention return shape details or filter combination semantics, but the schema and annotations cover most needs.

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?

All 9 parameters are fully documented in the schema with units, constraints, and guidance. The description only mentions 'rim dimensions and centre bore range' at a high level, so it adds no parameter-specific meaning beyond what the schema already provides.

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 clearly states the tool lists all bolt patterns (PCD) in the database, optionally filtered. It specifies the output format with an example and explicitly distinguishes itself from sibling list tools by focusing on bolt patterns and linking to search-by-rim.

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?

Explicitly recommends using this tool to discover valid bolt_pattern values before calling search-by-rim, giving a clear when-to-use. It doesn't provide explicit when-not-to-use guidance, but the named alternative and sibling context suffice.

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