list-rim-centre-bores

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds behavioral context by explaining it lists all 'available' CB values, describes the filtering semantics, and defines what CB is. It does not contradict annotations, though it omits details like result format or pagination.

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 sentences, front-loaded with the action, and contains no fluff. Every sentence adds value: the first states the function and filters, the second explains the metric and its downstream use.

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?

Despite no output schema, the description covers purpose, filter options, the definition of CB, and the intended usage scenario. Parameter details are handled by the rich schema. A slight gap is the lack of return format, but for a simple list tool this is acceptable.

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 coverage is 100%, with each parameter already having a detailed description. The tool description only groups filters conceptually ('rim dimensions, offset range, bolt pattern') without adding syntax or format details beyond the schema. Baseline 3 is appropriate.

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 'List all centre bore (CB) values available, optionally filtered by rim dimensions, offset range, and bolt pattern' – a clear verb+resource with scope. It also explicitly distinguishes the tool by saying 'Use this to discover valid cb values for search-by-rim', differentiating it from sibling list tools.

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 provides a clear usage directive: 'Use this to discover valid cb values for search-by-rim'. It does not explicitly mention when to avoid alternatives or compare to sibling tools, but the context is sufficient for most cases.

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