mknod

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

Descriptions add beyond annotations: highlights destructive nature, privilege requirements, dry-run behavior, and return format (JSON with path and type), without contradicting the destructiveHint annotation.

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?

Concise, every sentence adds value, front-loaded with purpose, well-structured.

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 5 params, no output schema, and annotations, the description covers purpose, usage, behavior, and return info adequately.

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 coverage is 100%, baseline 3 is appropriate. Description mentions dry-run and return JSON but doesn't add meaning to individual parameters beyond schema.

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?

Description clearly states it creates device nodes with dry-run support, and explicitly distinguishes from FIFO pipes (use mkfifo) and regular files (use touch), differentiating it from siblings.

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 explicit when-to-use (device files) and when-not-to-use (FIFO, regular files) with alternatives, mentions dry-run preview, elevated privileges, and references mkfifo.

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