fetch_records

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

Discloses truncation with max_chars and the 'truncated' flag, and mentions records can be large. However, with no annotations, it does not explicitly state that the tool is read-only or address authentication/rate limits, which are common behavioral concerns.

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?

Description is concise, front-loads purpose and warning, uses bullet points and examples efficiently. Every sentence contributes 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?

Covers key aspects like database-specific formats and truncation, but lacks details on ids format (e.g., comma-separated) and does not explain the full output schema despite its existence. Adequate but with gaps.

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 compensates well by explaining rettype/retmode combinations for multiple databases, max_chars truncation, and providing examples. Adds significant meaning beyond schema, though db and ids format are not fully elaborated.

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?

Clearly states 'Fetch full records' as verb+resource. Provides database-specific context but does not explicitly differentiate from sibling tools like get_summaries or get_full_text, though the purpose is evident.

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?

Includes warning 'USE SPARINGLY' and database-specific rettype/retmode combinations. However, lacks explicit guidance on when to use alternatives or when not to use, leaving usage context implied.

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