generate_prospecting_list

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

With no annotations provided, the description carries full burden for behavioral transparency. It discloses the premium nature and API key requirement, but does not detail potential side effects (e.g., data creation, cost) or whether the tool is read-only. More context on what happens during generation would improve 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?

Two sentences effectively convey purpose and key constraints. No filler words. The critical information is front-loaded, making it easy for an AI agent to parse quickly.

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 the tool's simplicity (2 parameters, no nested objects or output schema), the description is largely complete. However, it does not specify the format or content of the generated prospect list (e.g., names, LinkedIn URLs), which could be useful for an agent. Slight gap, but still functional.

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 for both parameters (icp_description and count). The tool description adds 'PREMIUM' and 'Requires DEESEEK_API_KEY' but does not elaborate on parameter usage beyond what the schema provides. Baseline is appropriate; no significant additional 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 tool's action: 'Generate a list of prospects based on your ICP'. The verb 'generate' and resource 'list of prospects' are specific. It distinguishes from sibling tools like search_public_profiles, which searches existing profiles rather than generating a list from an ICP description.

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 notes that the tool is 'PREMIUM' and 'Requires DEESEEK_API_KEY', providing important usage constraints. However, it does not explicitly state when to use this tool versus siblings like search_public_profiles or analyze_company, though the ICP-based generation implies a specific use case.

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