calibre_search_text

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

With no annotations, the description carries full burden. It does not disclose whether search is case-sensitive, supports operators, or any performance/rate limitations. No mention of index requirements or result behavior beyond 'snippets'.

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?

Single sentence, concise and front-loaded with verb and resource. Could be slightly more informative without losing conciseness, but no wasted words.

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?

Insufficient for a 3-parameter tool with no annotations and no schema descriptions. Fails to explain snippet format, search syntax, or relationship to other index tools. Expected more detail given the complexity.

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 description must compensate. It only implies 'query' but does not explain 'limit' or 'snippet_chars' beyond defaults. No clarification of what snippet_chars controls (character count around match).

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') and resource ('extracted full text from indexed Calibre books') and clearly states the outcome ('return snippets'). It effectively distinguishes from siblings like 'calibre_search_books' which likely searches metadata.

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?

No guidance on when to use this tool vs alternatives such as 'calibre_search_books' or prerequisites like needing an index (hinted by 'calibre_index_status' sibling). The description lacks context for appropriate usage.

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