search_literature

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

Discloses that it searches a specific SQLite table (library_seeded) and returns a markdown table. Also describes error behavior for missing database/table/column or no results. Lacks explicit read-only/destructive hint, but annotations are absent so description carries full burden. A slight gap is not stating side-effect profile, but it's implied to be read-only

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?

Efficient and well-structured: clear opening sentence, bullet-like sibling differentiation, parameter documentation, and return description. Every sentence adds value without redundancy

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?

Complete for the tool's complexity: covers purpose, usage, parameters, return format, and error handling. Output schema exists (not shown) but description adequately explains returns. No missing critical info for a search tool

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?

Adds meaning beyond schema: describes query as case-insensitive substring, field as column with enumerated values (all, disease, method, geography, article), and limit with default. Schema only provides types and defaults, so description adds value. Could be more precise about allowed field values but still helpful

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?

Clear verb-resource combination: 'Search the user's literature database.' Specifies the resource (curated/seeded literature catalogue) and the action. Explicitly distinguishes from three sibling tools (search_library, search_fulltext, search_pdf_knowledge).

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?

Provides explicit when-to-use and alternatives: states when to use this tool vs. search_library, search_fulltext, and search_pdf_knowledge. No when-not-to-use is needed as the guidance is clear

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