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

Annotations already declare write (readOnlyHint=false), non-destructive, non-idempotent, and closed-world. The description adds that the note originates from the current chat and can be filed under a chosen context, which is useful behavioral context beyond the safety profile. It does not, however, disclose the duplicate-creating consequence of non-idempotency or any auth/rate-limit details, so a 3 fits with annotations covering the basics.

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?

A single, front-loaded sentence with zero filler. Every word earns its place for a simple create tool.

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 create tool with full schema coverage and annotations, the description covers the core purpose but omits usage guidance, return behavior (no output schema), and idempotency implications. It is minimally adequate but leaves gaps an agent might need when deciding to call it.

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 100%, so the schema fully documents text, labels, and context_id. The description mentions context placement and optional labels, but adds no syntax, format, or constraint details beyond the schema. Baseline 3 applies.

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?

States a specific verb 'Create' and resource 'note', plus scope 'from this chat' and placement in a chosen context. It does not explicitly distinguish itself from siblings like contextli_add_label_to_note or the read tools, but the creation intent is unambiguous.

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 gives no when-to-use guidance or alternatives. It implies the action is creating a note, but an agent gets no help on when to choose this over adding a label, searching, or filtering. The schema's context_id description carries a usage hint, but that is outside the description itself.

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