Add an idea to your favorites/watchlist, or remove it if it is already there. Use it to bookmark marketplace ideas you want to revisit. Not read-only and deliberately not idempotent, since each call flips the current state.
| Name | Required | Description | Default |
|---|---|---|---|
| ideaId | Yes | The idea 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?
Explicitly states that the tool is not read-only, not idempotent, and flips state on each call. This goes beyond annotations (which already set readOnlyHint=false, idempotentHint=false) by explaining the flip behavior, which is critical for correct agent usage.
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?
Three sentences, each earning its place: action, usage context, behavioral trait. No unnecessary words, front-loaded with purpose.
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?
For a simple toggle tool with annotations and output schema present, the description covers purpose, usage, and behavioral transparency. No missing critical information for invocation.
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 covers the single parameter 'ideaId' with description 'The idea ID'. The tool description adds no additional meaning about the parameter, so it meets the baseline for 100% schema coverage.
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?
Clearly states the tool toggles favorite status of an idea, using specific verbs 'add' and 'remove'. Distinguishes itself from siblings by being a toggle operation rather than a read, create, or delete.
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 context: 'Use it to bookmark marketplace ideas you want to revisit.' This tells the agent when to invoke it. However, it does not explicitly mention when not to use it or point to an alternative tool.
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.
