NOUZ MCP Server

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

No annotations provided, so description carries full disclosure burden. 'Write' is ambiguous: does it overwrite existing files? Does it create parent directories? How is metadata serialized into YAML? No behavioral traits disclosed beyond the upfront mention of frontmatter.

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?

Extremely brief (4 words) and front-loaded, but brevity undermines clarity for a 3-parameter mutation tool. Single sentence structure wastes no space, yet lacks necessary elaboration given the complexity (nested object, no output schema).

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?

Inadequate for a file-writing tool with nested object parameters and no output schema. Missing critical safety information (destructive potential, path resolution rules) and operational details (encoding, atomicity). Description leaves agent guessing about failure modes and exact frontmatter construction.

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 0% description coverage. Description mentions 'YAML frontmatter' implying metadata parameter purpose, but fails to explain path format expectations (absolute/relative?), content structure (should it exclude frontmatter?), or how the metadata object maps to YAML. Insufficient compensation for schema gaps.

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 specific verb (Write) and resource (file), and mentions distinct feature (YAML frontmatter). Differentiates from sibling read_file by action direction. Loses point for not clarifying if this creates, overwrites, or appends.

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?

Provides no guidance on when to use versus alternatives (like read_file), prerequisites (directory must exist?), or safety warnings about overwriting existing files. Agent must infer usage from parameter names alone.

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