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

The annotations already establish that the tool is read-only, idempotent, and non-destructive. The description adds that the guidance is Knobs.co-specific and rules-based, but it does not clarify whether the content is static, how current it is, or what form the response takes; "No arguments" merely repeats the schema.

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 compact and front-loaded, efficiently communicating both the source and the guide's practical scope. Its closing invocation note is brief, and there is no substantial filler.

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?

This is sufficient to select and invoke a simple zero-argument reference tool, especially with its safety profile supplied by annotations. With no output schema, it could be slightly more complete by stating that it returns general guidance rather than personalized calculations or product-specific fit verification.

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?

There are no parameters, so the baseline is 4 and no further parameter documentation is necessary. The explicit "No arguments" statement confirms simple invocation but adds nothing beyond the empty schema.

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 identifies the resource as Knobs.co's cabinet-hardware sizing rules and enumerates concrete topics, including pull length, drawer width, knobs versus pulls, and hole measurement. It does not explicitly differentiate the guide from siblings such as ask_sienna or get_product.

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 topic list provides clear usage context for choosing hardware sizes and configurations or measuring existing holes. It does not explicitly say when to use this general guide instead of asking ask_sienna or retrieving product-specific information.

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