Capture a Brain Dump

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

Beyond the annotations, the description discloses the storage target (tenant-scoped Boardroom Ideas table), the downstream side effect (ACK-tracked Continuous Improvement triage), the return value (triage deadline), and availability scope. This is solid context for a non-idempotent write, though it doesn't mention duplicate handling or failure modes.

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?

Front-loaded with the core purpose before the operational details, and every sentence contributes (purpose, timing, storage, consequence, return, access, required param). It's dense and slightly comma-heavy but not padded.

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?

With no output schema, the description compensates by naming the returned triage deadline, plus the storage destination and triage side effect. An agent has enough to invoke it correctly; only error/duplicate behavior is unaddressed.

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 75%, so most parameters are already documented in the schema. The description adds some framing ('one rough sentence is enough', 'agent_id required') but says nothing about the kind enum values or the context pointer, so it adds only marginal value over 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 opens with a specific verb and resource ('Fast intake for an idea, pain point, workaround, or frustration') that tells an agent exactly what gets captured. It does not name siblings like list_brain_dumps or triage_brain_dump, but the emphasis on quick capture vs later triage implicitly separates it from them.

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?

'Use it immediately while doing other work; one rough sentence is enough and no solution is required' gives concrete when-to-use guidance and lowers the bar for capturing. It stops short of explicitly naming alternatives or exclusions, so it earns a 4 rather than a 5.

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