ora_capture_note

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

No annotations exist, so the description must cover behavioral traits. It states the tool captures a note (a write operation), but does not disclose whether it is destructive, idempotent, requires special permissions, or what side effects occur. Basic action is clear, but deeper behavioral context is missing.

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 sentence plus a brief note, front-loading the action and trigger. No superfluous text; every word contributes to understanding.

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 tool's simplicity (3 params, no output schema), the description covers purpose, trigger, and format. However, it omits what happens after capture (e.g., confirmation, storage location) and does not leverage the absence of annotations to add behavioral completeness. Adequate but not thorough.

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%, so the baseline is 3. The description adds value by recommending a content structure ('problème → solution'), which extends beyond the schema's description. Tags and project_path are not further clarified, but overall the description enriches the content parameter's usage.

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 it captures a note/solution in ORA memory, with a specific trigger (user writing /ora :: [content]). It implies differentiation from sibling capture tools like ora_capture_decision by specifying 'note/solution', though it doesn't explicitly compare.

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 indicates when to use (when user writes /ora :: [content]) and recommends a format, but does not provide when-not-to-use guidance or mention alternatives among the many sibling capture tools.

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