capture_idea

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

No annotations are provided, so the description carries the full burden. It discloses where the note is saved (existing project's seeds or Quick Notes library) but does not detail side effects, auth requirements, or potential destructive actions. Additional context would be beneficial.

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 a single, front-loaded paragraph of about three sentences. It includes examples and exclusions without any fluff, making it efficient and focused.

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 capture tool, the description covers purpose, usage guidelines, and parameter behavior. However, it lacks information about return values or confirmation of action, which is acceptable given no output schema, but could be slightly more complete.

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 all three parameters. The description adds value by explaining that projectName is inferred if omitted (default behavior) and clarifies the role of workspaceId, going 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's purpose: capturing quick notes or seeds into projects or Quick Notes. It distinguishes from sibling tool idea_kickoff by specifying that this is for lightweight 'remember this' notes, not full venture ideas.

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 explicitly states when to use (lightweight 'remember this' notes with example phrases) and when not to use (new business ideas), and directs to idea_kickoff as alternative. It even advises to prefer idea_kickoff when unsure.

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