list_records

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

No annotations provided, so description bears full burden. It mentions pagination and field selection but does not disclose error handling, rate limits, or behavior on invalid modules. Lacks richer behavioral context beyond the obvious list operation.

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 (3-line purpose + args), front-loaded, and each sentence adds value. Slightly improved by adding usage guidance, but currently efficient.

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 existence of output schema, description need not detail return values. It adequately covers parameters and basic behavior, but lacks completeness in distinguishing from sibling tools and handling edge cases.

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 coverage is 0%, and description adds meaning to all 4 parameters: module with examples, fields as optional subset, page as 1-indexed, per_page with max limit of 200 from Zoho CRM v6, providing helpful context beyond the 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 'List records from a Zoho CRM module' using a specific verb and resource. It effectively distinguishes from siblings like 'get_record' (single record), 'search_records', and 'list_related_records'.

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 provides parameter guidance but lacks explicit when-to-use vs alternatives (e.g., vs 'search_records' for filtering). It describes pagination with page/per_page but no exclusions or prerequisites.

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