capture_note

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

With no annotations, the description carries the behavioral burden. It discloses the create-then-write sequence and the conditional body behavior ('si fourni'), but it does not cover edge behavior such as folder handling or what happens on duplicate titles. Still, the core creation behavior is clear.

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 efficient sentence with a clear sequence and no filler. It could be slightly more structured to cover folder behavior, but as written it is compact and front-loaded.

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 simple 3-parameter shape and the existence of an output schema, the description covers the basic invocation path. It is incomplete for an agent choosing among many note-writing siblings and for understanding the folder default, but it is adequate for a straightforward capture call.

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 description coverage is 0%, so the description must compensate. It clarifies the body parameter is only written when provided, but it gives no explanation of the folder parameter or its 'quick' default, leaving two of three parameters semantically under-documented.

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 states a clear action: 'cree une note puis y ecrit le body' (creates a note then writes the body), so an agent knows the core purpose. It is specific about the resource (note) and the write behavior, but it does not explicitly differentiate itself from sibling create_note/write_note.

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?

There is no guidance about when to use this over create_note, write_note, or append_to_note. 'Capture rapide' only suggests speed; it does not state conditions or alternatives.

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