Save Markdown note

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

No annotations provided, so description carries full burden. Mentions saving to NOTES_DATA_DIR and returning metadata/file resource, but fails to disclose overwrite behavior, file naming, or permission requirements. For a mutation tool, these are significant omissions.

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?

Single sentence conveying action, destination, and return value. No redundant phrasing.

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?

Tool is a write operation with no annotations, no output schema, and poorly documented parameters. While it mentions return value, it lacks usage guidance, side-effect disclosure, and parameter detail, making it incomplete for reliable agent invocation.

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 has zero property descriptions, and the description does not explain title, content, or tags. Only indirect hint is 'Markdown' which could correspond to content format. No semantic elaboration beyond 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?

States clearly that the tool saves a Markdown note/report to NOTES_DATA_DIR and returns metadata plus the saved file resource. The verb 'save' distinguishes it from sibling read/list tools.

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?

Description implies a write operation but does not explicitly state when to prefer this over notes_read or notes_list. No exclusion or alternative guidance given.

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