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

With no annotations, the description carries the disclosure burden. It states return fields (name, category, tier, pricing, availability, link), which is helpful. However, it does not explicitly mention that this is a read-only operation, potential side effects, or any constraints like pagination or rate limits. The 'search' verb implies read-only, but the transparency is minimal.

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 concise sentences, front-loaded with the core purpose. No redundant information or filler. Every sentence contributes to understanding.

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 2-parameter search tool with no output schema, the description adequately covers return values and filter options. It lacks details such as combination semantics, but given the simplicity, it is reasonably complete. The return fields are explicitly listed, which is essential when no output schema is present.

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 the baseline is 3. The description adds example values (violin, flute for category; strings, woodwind for family) but these are similar to the schema examples. It does not clarify whether both filters can be used together or how they combine, so it adds minimal value beyond the 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 uses the specific verb 'Search' with a clear resource: 'instruments available for rental at Prelude NZ'. It also mentions filtering by category or family, making it distinct from sibling tools like get-faqs-tool, get-pricing-tool, and search-teachers-tool.

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 clearly indicates when to use this tool: when searching for rental instruments, with optional filters. It does not explicitly exclude alternatives, but the specificity of 'instruments' and the visible sibling names make the context clear. It lacks explicit 'use this instead of X' guidance, so not a 5.

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