chown

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

Discloses destructive behavior ('modifies filesystem ownership metadata'), may require elevated privileges, and recommends using --dry_run to preview. Annotations only state destructiveHint: true, so description adds valuable context without contradiction.

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?

Five sentences with no fluff; first sentence immediately states core function and dry-run support. Each sentence adds unique value, and the structure is front-loaded with key information.

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?

Covers purpose, usage guidance, behavioral traits, and parameter hint (dry_run). No output schema exists, but description mentions JSON return. Could elaborate on owner parameter syntax but schema already does that. Sufficient for a tool with moderate complexity.

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 baseline is 3. Description mentions dry-run support but does not add meaning beyond what the schema already provides for the parameters. No additional parameter details are given.

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 tool changes file user ownership with dry-run support, using specific verb and resource. It distinguishes itself from siblings by mentioning 'chgrp' and 'chmod' for alternative operations.

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?

Explicitly provides when-to-use ('transfer file ownership between users') and when-not-to-use ('Not for group-only changes ... Not for permission changes') with named alternatives ('chgrp', 'chmod').

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