SmartProspect: get already-fetched contacts

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

Adds substantial behavioral context beyond annotations: explicitly states it does not consume SmartProspect credits, creates or modifies no remote state, cannot send email, and is destructive: no. This goes beyond readOnlyHint and gives concrete operational details.

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 compact and well-structured, front-loading the core purpose in the first sentence and then providing safety and usage constraints. Each sentence adds unique information, with only minor redundancy around read-only status.

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 8 parameters, full schema descriptions, and an output schema, the description covers all essential aspects: purpose, safety profile, endpoint, parameter selection rules, and scoping of filters. No critical gaps remain for effective use.

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 descriptions, so baseline is 3. The description adds extra value by centralizing the mutual exclusivity rule and specifying that limit, offset, search, verification_status, and catch_all_status apply only when using filter_id, which is not fully apparent from individual parameter descriptions.

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 retrieves already-saved or fetched contacts, using a specific verb ('Retrieve') and resource ('contacts'). It distinguishes from siblings like smartprospect_fetch_contacts by explicitly noting these are already paid for and no credits are spent.

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 clear context: use this for already-fetched contacts without spending credits and states the constraint to provide exactly one of id or filter_id. It does not explicitly name alternative tools for when-not-to-use, but the 'already fetched' phrasing and credit-saving implication serve as implicit guidance.

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