list-rim-offsets

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

Annotations already declare readOnlyHint=true, so the read-only nature is known. The description adds behavioral context by explaining the meaning of offset values (positive = hub-centric, negative = deep dish) and the available filters, going beyond annotation-provided facts without contradicting them.

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: the first states the operation and filters, the second defines the key term. There is no wasted language, and the most actionable information is front-loaded.

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 listing tool with no required parameters and no output schema, the description adequately covers purpose, filters, and domain terminology. It could explicitly state the return format (e.g., a list of numbers), but the context is sufficient for an agent to select and invoke the tool correctly.

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%, so all four parameters have detailed descriptions. The tool description merely references rim diameter, width, and bolt pattern without adding new meaning; the schema already explains each parameter's type, format, and constraints. Baseline of 3 applies.

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's function: 'List all rim offset (ET) values available' with optional filters. It distinguishes from sibling list tools (e.g., diameters, widths, bolt patterns) by explicitly focusing on rim offsets and providing a domain-specific definition of ET.

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 gives explicit usage guidance: 'Use this to discover valid rim_offset values.' It also implies filters for other attributes, but does not explicitly name alternatives or when-not-to-use cases, though the sibling tools are evident from context.

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