搜索图书

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavioral context by specifying that the search operates on title, author, or tag fields, which goes beyond the schema's simple 'query' string. It does not disclose pagination or result ordering, but this is minor for a simple search tool.

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 a single, compact sentence that delivers the essential information immediately. Every word earns its place and there is no redundant or filler content.

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 two-parameter search tool with an output schema and safety-revealing annotations, the description provides sufficient context to call the tool correctly. The search criteria are specified, required parameters are evident from the schema, and the output schema covers return values. Nothing critical is missing.

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 description coverage is 0%, so the description must compensate for the underspecified 'query' parameter. It does so by clarifying that query can be a title, author, or tag. However, it does not explain the 'limit' parameter at all; although the default value provides some hint, the description leaves that semantic gap open.

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 a specific verb ('search') with a clear resource ('book catalog/bibliography') and explicitly lists the searchable criteria (title, author, or tag). This makes it easily distinguishable from the sibling tools, which are mutations or inventory audits.

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 implies this tool is for finding books by title, author, or tag, which sets context against the mutation siblings (checkout_book, return_book). It does not explicitly state when not to use it or provide alternative selection criteria, but the sibling names make the distinction obvious enough.

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