ln

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

Description reveals destructive nature ('creates filesystem links') consistent with destructiveHint annotation. Adds details on overwrite protection (default enabled), dry-run preview, and JSON return format.

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 concise (3 sentences) with no wasted words. Front-loaded with key purpose and options.

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?

Despite no output schema, description states return value format. All 6 parameters are covered in schema and description adds behavioral context. Complete for a link-creation tool with clear annotations.

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%, but description adds meaning beyond schema by explaining --symbolic for cross-filesystem/directory symlinks, default overwrite protection behavior, and dry-run purpose.

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 'Create hard or symbolic links' and distinguishes from sibling tools like 'link' and 'cp' by specifying use cases and exclusions. It uses specific verbs and resources.

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?

Explicit guidance on when to use (filesystem aliases) and when not (hard-link-only operations use 'link', copying use 'cp'). Also mentions dry-run and overwrite protection options.

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