List B2B leads with business names, opportunity scores and status, optionally filtered by campaign. Use it to triage which leads to work next. Read-only and free. Admin only.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max leads to return | |
| campaignId | No | Filter by campaign ID |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | The tool result rendered as human and AI readable text or markdown. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, so the description's 'Read-only' is redundant. However, it adds valuable behavioral context: 'free' (no cost) and 'Admin only' (role restriction). These go beyond the annotations and help the agent understand 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 extremely concise—four short sentences, each adding distinct value. It is front-loaded with the purpose, then provides usage guidance, then behavioral traits. No wasted words.
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 low complexity (2 optional params, output schema present, annotations provided), the description covers all necessary aspects: purpose, usage, constraints (admin only, read-only, free) and key output fields. No obvious gaps.
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 description coverage is 100%, so the baseline is 3. The description mentions 'optionally filtered by campaign' but this repeats the schema's campaignId field. No additional parameter semantics (e.g., format, usage tips) are provided beyond the schema.
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 lists B2B leads with specific fields (business names, opportunity scores, status) and supports optional campaign filtering. This distinguishes it from sibling tools like get_b2b_lead (single lead) and get_b2b_stats (aggregated stats).
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 provides a clear use case: 'triage which leads to work next.' However, it does not explicitly mention when not to use this tool or offer alternatives. The context is well-defined but lacks exclusionary guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct function or data aspect, from idea CRUD to simulations, content generation, and team management. Despite the large number, descriptions clearly differentiate purposes, e.g., 'get_idea_summary' vs. 'get_idea_agents' vs. 'get_idea_evolution'. No two tools appear to do the same thing.
All tools follow a consistent verb_noun pattern in snake_case (e.g., 'create_idea', 'get_competitive_density', 'toggle_favorite'). No mixing of conventions like camelCase or abbreviations. The pattern is uniform and predictable.
63 tools is far beyond the typical well-scoped range of 3-15. While the platform's broad scope (idea validation, B2B, team, simulations) justifies many, the sheer volume can overwhelm an agent. A more curated subset or grouping would improve coherence.
The tool set covers the full startup idea lifecycle: creation, validation, retrieval of various analyses, updates, deletion, sharing, simulations, B2B lead generation, team collaboration, and market intelligence. No obvious gaps exist for the stated domain.
