Note

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

The description indicates notes are managed and scoped, and the readOnlyHint is already false, so there is no contradiction. However, it does not disclose whether actions permanently delete or only update notes, and no output behavior is mentioned, leaving some behavioral details implicit.

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 brief, front-loaded with the core purpose, and uses a clear 'Use when' / 'Do NOT use when' structure. Every sentence contributes directly to orienting the agent.

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?

The description places notes in the broader context of scratch state versus durable lore, which is important given sibling lore and world tools. It does not explicitly explain required parameters for actions like set or the return format, but the schema and enums fill most 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?

The schema covers all parameters with descriptions and enums, so the description adds little beyond that. The parameter descriptions are mostly tautological, and the tool description does not clarify parameter relationships (e.g., which parameters apply to which actions), but schema coverage is complete.

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 identifies the resource as Novel-scoped notes and distinguishes its purpose from lore by framing it as scratch state. The verb 'Manage' is somewhat generic, but the explicit 'Use when' / 'Do NOT use when' contrast with lore makes the intended purpose clear.

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 provides explicit guidance on when to use the tool ('storing scratch state the caller will reuse') and when not to use it, directing to lore instead. This makes the tool's appropriate usage unambiguous relative to sibling tools.

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