SmartProspect: list fetched searches

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

Beyond annotations (readOnlyHint, destructiveHint), the description adds critical safety context: no SmartProspect credit consumption, no remote state modification, no email sending, and the fact that contacts were already paid for. This provides a complete safety profile without requiring the agent to infer from annotations alone.

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 somewhat verbose with repetitive safety statements, but each sentence adds unique value (purpose, safety, endpoint, alternative). It is well-structured and easy to scan, though it could be tightened without losing meaning.

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 fully contextualized: purpose, safety, endpoint, relation to paid contacts, and the recommended companion tool for retrieval. An output schema exists, so return-value details are not needed in the description.

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 100% with clear descriptions for both limit and offset. The description does not add parameter-specific semantics beyond what the schema already provides, so the baseline 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 specifies the exact resource ('searches whose contacts have already been fetched') and includes per-filter fetch metrics, clearly distinguishing it from sibling tools like list_saved_searches and list_recent_searches. The verb 'List' is concrete and actionable.

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?

Explicit guidance is given: 'Contacts listed here were already paid for; retrieve them with smartprospect_get_contacts rather than fetching again.' This tells the agent when to use this tool versus alternatives, and also states the tool is free and read-only.

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