get-list-entries

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

With no annotations provided, the description carries full burden but only states what the tool does without disclosing behavioral traits such as pagination behavior (implied by offset/limit but not explained), rate limits, authentication needs, or error handling. It mentions 'companies, people, etc.' but doesn't clarify if this is exhaustive or example-based.

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 a single, efficient sentence that front-loads the core purpose with zero waste. It uses parentheses to add clarifying examples without bloating the text.

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 read operation with 3 parameters and 100% schema coverage but no annotations or output schema, the description is minimally adequate. It covers the basic purpose but lacks details on return values, error cases, or behavioral context that would help an agent use it effectively.

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 100%, so the schema fully documents parameters (listId, limit, offset). The description adds no additional parameter semantics beyond what's in the schema, such as format details for listId or constraints on limit/offset values.

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 verb 'Get' and resource 'entries for a specific CRM list', with examples like 'companies, people, etc. in sales pipelines' that clarify the type of data. It distinguishes from general search tools but doesn't explicitly differentiate from sibling tools like 'filter-list-entries' or 'advanced-filter-list-entries'.

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?

No guidance on when to use this tool versus alternatives like 'filter-list-entries', 'advanced-filter-list-entries', or 'search' tools is provided. The description implies usage for retrieving list entries but lacks explicit context or exclusions.

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