notlai_create_note

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only mentions Markdown support, which is already detailed in the input schema. It lacks information about authentication, idempotency, side effects (e.g., whether a note ID is returned), or rate limits.

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 two sentences long, with no redundant information. The first sentence clearly states the purpose, and the second provides a useful usage hint. Every sentence is justified.

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 has 4 parameters, no output schema, and no annotations, the description is somewhat incomplete. It does not explain the return value (e.g., note ID), authentication prerequisites, or error handling. However, it does cover the main purpose and provides a workflow hint.

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?

The input schema has 100% description coverage for all 4 parameters, so the baseline is 3. The description adds value only for the 'tags' parameter by suggesting a workflow (use notlai_list_tags), but does not enhance understanding of other parameters like 'isFavorite' or 'content' beyond what is already in 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 clearly states 'Create a new note', specifying the verb and resource. It also mentions Markdown formatting support and suggests using notlai_list_tags for tag assignment, which distinguishes it from sibling tools like notlai_update_note or notlai_delete_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?

The description gives explicit guidance to 'consider using notlai_list_tags to find relevant tags to assign' before creating a note. However, it does not mention when not to use this tool or provide direct comparisons to alternatives like notlai_update_note.

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