Capture Thought

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

No annotations are provided, so the description must carry the burden. It discloses the target folder and that no structure is required, which is helpful, but it doesn't explain other side effects like file creation behavior, collision handling, or permissions. This leaves some gaps in understanding the tool's exact behavior.

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, front-loaded with the key action, no fluff. Every word earns its place.

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?

The tool is simple and well-described for its purpose. The schema covers parameters, and the description provides usage context and target location. Since there is no output schema, explaining return values is unnecessary. It's sufficiently complete, though a note about it being a write operation could be added.

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?

All four parameters are fully described in the schema (100% coverage), so the description doesn't need to add much. The phrase 'No structure required' reinforces that content can be free-form, and 'title' and 'content' are self-explanatory. The description adds minimal extra meaning 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 uses the specific verb 'capture' and identifies the resource as a thought/idea/brain dump saved to the Ideas/ folder. It clearly distinguishes from sibling tools like create_note and create_prd by emphasizing quick, unstructured capture.

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?

Explicitly states when to use it: 'fleeting ideas, shower thoughts, or anything that needs to be captured fast.' It doesn't explicitly name alternatives or when-not-to-use, but the context is clear enough to guide an agent.

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