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

Annotations already disclose the write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false) and that the call is not idempotent. The description adds a little lifecycle context (the note is retained for future conversations) but never warns that repeat calls with identical content create duplicate nodes, nor whether writes require auth or are permanent.

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?

One front-loaded sentence with a clear verb, resource, and purpose clause. Nothing is padded or redundant.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. However, for a 5-parameter mutation tool at 40% schema coverage, the description is too thin: it omits duplicate/idempotency behavior and gives no help on the undocumented content/tag/title parameters.

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 only 40% — type and parentId are documented, while content, tag, and title are bare. The description adds no parameter meaning whatsoever (no tag semantics, no nesting behavior, no note-type guidance), so it fails to compensate for the coverage gap.

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 ("Store") and resource ("a note in the user's CortexPlus memory"), plus the downstream benefit (recall in future conversations). It implicitly contrasts with retrieval siblings like recall/search, but never names them, so an agent must infer the distinction.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as recall, save_context, or memory. Only the phrase "so future conversations can recall it" hints at intent, leaving the agent to infer when this beats the sibling tools.

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