Create a note

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

The description simply restates the tool's action without additional behavioral context. Annotations already indicate it is a write operation (readOnlyHint=false), so the description adds no value beyond the structured fields.

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, making it concise. However, it omits important information (e.g., notebook parameter), which reduces effectiveness. It could be restructured to front-load the required notebook context.

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 tool with 3 required parameters and no output schema, the description is incomplete. It does not mention the notebook parameter or describe return values or side effects. Given the complexity, more detail is needed.

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 low (33%, only notebook has description). The description mentions 'title and content' but does not explain their format, constraints, or behavior. It adds minimal semantic value beyond the parameter names.

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 creates a note with title and content, but fails to mention the required 'notebook' parameter, which is essential for understanding the tool's purpose. It is a specific verb+resource but not fully complete.

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?

No guidance on when to use this tool versus siblings like note_update or note_delete. No prerequisites, conditions, or exclusions are provided.

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