List records in a view

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

No annotations are provided, so the description must disclose the behavioral profile. It mentions listing and pagination but does not describe the response format, sorting, authorization requirements, rate limits, or any other side effects. For a read operation, this is minimal transparency.

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 two sentences, front-loaded with the core function and a practical prerequisite. It is concise with no filler, achieving high information density.

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 no output schema and no annotations, the description omits the return structure and any additional filtering or sorting behaviors. It covers the essential action and pagination but leaves the agent guessing about response fields and edge cases. It is adequate but not comprehensive.

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 low (25%). The description adds context that view_id comes from freshsales_list_views and lists the record types, which maps to the module enum. However, it does not elaborate on page or per_page semantics beyond what the schema already provides via defaults and minimum/maximum. The added value is moderate.

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 tool lists records of multiple types (leads, contacts, deals, accounts, tasks, appointments) belonging to a saved view, with pagination. This distinguishes it from sibling tools like freshsales_search (which searches across criteria) and freshsales_get_record (which retrieves a single record).

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 a useful prerequisite: 'Get view_id from freshsales_list_views first.' However, it does not explicitly explain when to use this tool versus freshsales_search for dynamic queries, nor does it state when not to use it. Usage guidance is implied but not explicit.

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