search

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

With no annotations provided, the description carries the full burden. It discloses some behavioral traits like case-insensitive operators, lack of parentheses support, and default values for max_results and include_bibtex. However, it misses details like rate limits, error handling, or authentication needs, leaving gaps for a tool with 6 parameters.

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 appropriately sized and front-loaded with the core purpose, followed by a structured breakdown of arguments and returns. Every sentence adds value, though the parameter explanations could be slightly more concise.

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 search tool with 6 parameters, no annotations, and no output schema, the description is largely complete. It covers purpose, parameters with semantics, and return format. Minor gaps include lack of pagination details or explicit error cases, but it adequately supports agent usage.

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?

Given 0% schema description coverage, the description fully compensates by providing detailed semantics for all 6 parameters. It explains the query format with examples, optional status, defaults, and filtering logic (e.g., 'case-insensitive substring filter for publication venues'), adding significant value beyond the bare 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 states the specific action ('Search DBLP for publications') and resource ('publications'), distinguishing it from siblings like 'get_author_publications' or 'get_venue_info' by focusing on boolean query-based search rather than author-specific or venue-specific lookups.

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 implies usage through the mention of 'boolean query string' and parameter details, but does not explicitly state when to use this tool versus alternatives like 'fuzzy_title_search' or 'get_author_publications'. No exclusions or clear alternatives are provided.

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