mek_search_advanced

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

With no annotations, the description carries the full burden. It discloses important behavior: no server-side paging (MEK returns all hits, max_results only limits return), operator handling, and options like accent_insensitive and include_processing. It does not explicitly state read-only status, but the search context implies non-destructive usage.

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 moderately long but well-structured with an overview paragraph followed by a bullet-like Args list. Every sentence serves a purpose, though the Args list could be slightly more concise without losing clarity.

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?

Given the high parameter count (18), no output schema, and no annotations, the description comprehensively explains the tool's logic, parameters, and constraints. It lacks details on return format or error handling, but for a search tool, the coverage is strong.

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. It provides detailed explanations for all 18 parameters, including the multi-row structure, operator values ('and', 'or', 'not'), and the purpose of each field. However, it could clarify the exact format of field values (alias vs raw MEK) beyond referencing mek_list_search_fields.

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 'Advanced MEK bibliographic search with up to 5 field-specific criteria rows.' It uses a specific verb ('search') and resource ('MEK bibliographic'), and distinguishes itself from siblings (mek_search_simple, mek_search_fulltext) by emphasizing the multi-row, operator-based advanced nature.

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 explains the row-and-operator logic and refers to mek_list_search_fields for field values. It implicitly indicates this is for complex queries via the name 'advanced', but does not explicitly state when to use this tool versus simpler alternatives or provide exclusions.

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