FlowNoter MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: automatic filtering of tool calls/intermediate steps, markdown formatting, and file naming/saving location. However, it omits details like error handling, permissions, or rate limits, which are relevant for a write operation. The description doesn't contradict any annotations (none exist).

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 front-loaded with the core purpose in the first sentence, followed by essential details in a logical flow. Every sentence adds value: saving location, filtering behavior, and parameter guidance. It avoids redundancy and is appropriately sized for the tool's complexity, making it efficient to parse.

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?

Given the tool's moderate complexity (3 parameters, write operation) and lack of annotations/output schema, the description provides a solid foundation by covering purpose, behavior, and basic usage. It compensates well for missing structured data, though it could be more complete by addressing potential errors or output details. No sibling tools reduce contextual demands.

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 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'how many recent messages to include' (hinting at num_messages usage) and reinforcing the filtering behavior for messages. This meets the baseline for high schema coverage without significant enhancement.

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 the specific action ('save recent conversation messages as a markdown note'), resource ('notes folder'), and scope ('automatically filters out tool calls and intermediate processing steps'). It distinguishes this tool's purpose with precise details about what content is preserved and where it's saved, making it immediately actionable without ambiguity.

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 implies usage context ('recent conversation messages') and provides some guidance on parameter usage ('specify how many recent messages to include'), but it lacks explicit when-to-use directives, prerequisites, or comparisons to alternatives. Since no sibling tools are listed, the absence of differentiation is acceptable, but overall guidance remains basic.

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