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

The description states that notes are written in Markdown and that the tool should be used frequently, but it doesn't disclose whether successive calls replace or append to existing notes. Without annotations, this leaves an important behavioral gap about state persistence.

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?

Three concise sentences front-load the purpose, then give usage timing and formatting guidance. No filler or repetition of schema details.

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 two-parameter tool with full schema coverage, the description covers purpose, usage context, and formatting. It falls slightly short by not addressing persistence behavior, but overall it's sufficient for an agent to invoke the tool correctly.

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 schema already provides descriptions for both parameters (title and content), and the description reinforces that content should be Markdown. It adds value by suggesting use cases like organizing thoughts and planning steps, which helps the agent populate the content parameter meaningfully.

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 uses specific verbs ('write notes', 'organize your thoughts', 'plan steps') tied to a clear resource (scratchpad), making the tool's function unambiguous. It also signals when it's appropriate (complex problems), further clarifying its role.

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?

It explicitly advises using the scratchpad for complex problems and 'as often as needed throughout your work,' giving clear usage context. It doesn't provide exclusions or alternative tools, but with no siblings the guidance is sufficient.

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