get_saved_leads

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions the subscription requirement, lacking details on permissions, rate limits, response format, or pagination behavior. This is insufficient for a tool that likely involves data retrieval and potential constraints.

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 directly states the purpose and prerequisite without unnecessary words. It is front-loaded and appropriately sized for the tool's complexity.

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 annotations and no output schema, the description is incomplete. It fails to explain what the tool returns (e.g., lead details, pagination info) or other behavioral aspects like error handling. For a data retrieval tool with potential subscription dependencies, more context is needed.

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 input schema has 100% description coverage, with clear documentation for 'start' and 'count' parameters. The description adds no additional parameter information, so it meets the baseline score of 3, as the schema adequately covers the semantics.

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 ('Get') and resource ('saved leads from Sales Navigator'), making the purpose understandable. However, it doesn't differentiate this tool from sibling tools like 'get_lead_lists' or 'sales_search_leads', which might retrieve similar data, so it doesn't reach the highest score.

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 mentions a prerequisite ('requires Sales Navigator subscription'), which provides some context, but it doesn't specify when to use this tool versus alternatives like 'get_lead_lists' or 'sales_search_leads'. No explicit guidance on when-not-to-use or comparisons is given.

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