Create Note

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

No annotations are supplied, so the description carries the full behavioral burden. It says nothing about whether the notebook must exist, whether it needs write permission, what happens on duplicate titles, or what the created object contains. For a mutation tool with zero annotation coverage this is a notable gap, though the presence of an output schema softens the impact.

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?

Two short sentences with no waste; the core action is front-loaded and the helpful pointer follows. Every sentence earns its place.

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?

Because an output schema exists, return values need not be explained. However, for a three-parameter mutation tool with no annotations and no schema descriptions, the definition leaves the caller guessing about field semantics and preconditions. Adequate but with clear gaps.

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% and all three parameters (title, body, notebook_id) are undocumented in the schema. The description only implicitly tells us what a note is made of and explicitly points to list_notebooks for notebook_id, leaving title and body semantics unstated. It partially compensates for the coverage gap but does not resolve it.

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) with a scope qualifier (in the given notebook), which is clear on its own. It does not, however, distinguish itself from sibling create_notebook or explain how it differs from update_note beyond the obvious verb change.

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 second sentence gives concrete, actionable guidance: call list_notebooks to obtain a notebook_id. That covers the main prerequisite for a first-time caller. No when-not-to-use guidance or mention of failure cases is provided, so it falls short of a 5.

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