List saved views/filters

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

With no annotations provided, the description carries the burden of conveying the tool's safe read-only nature. The verb 'List' implies a read operation, but the description does not disclose details about return values, pagination, or any potential side effects. It adds the context of filtering examples, which helps, but remains minimal for a tool with no annotations.

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?

Two sentences with no fluff. The first sentence leads with the action and resource, the second adds purpose and a workflow tip. Every word earns its place.

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?

The tool is simple (single parameter, no output schema), and the description covers its core purpose and usage. It implicitly indicates that returning view_id is part of the result ('Use this to discover a view_id'), which is sufficient for this low-complexity tool. A score lower than 4 would be overly harsh given the context.

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?

The schema fully describes the 'module' parameter with an enum, achieving 100% coverage. The description does not add parameter-specific information beyond the schema, so the baseline score of 3 applies.

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 action ('List') and the resource ('saved views (filters) for a Freshsales module') with concrete examples ('My Leads', 'Open Deals'). It also differentiates from sibling tools by explicitly tying it to discovering a view_id for freshsales_list_records, which is distinct from listing records directly.

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?

Provides an explicit use case: 'Use this to discover a view_id before calling freshsales_list_records.' This effectively positions it relative to a sibling tool. However, it does not mention any when-not-to-use scenarios or alternative contexts, though sibling names imply other use cases.

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