chown_file

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

With no annotations provided, the description carries the full behavioral burden and delivers almost nothing: it does not disclose permission requirements, whether the change is reversible, what happens to files not owned by the caller, or the effect of the recursive flag. Only the bare mutation intent is conveyed.

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?

Three words are front-loaded and waste-free, but this is not genuine conciseness so much as under-specification. A useful description for a 4-parameter mutation tool cannot fit in a phrase this short.

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?

For a filesystem mutation with 4 parameters (one required boolean whose meaning is undisclosed), no annotations, and no output schema, the description omits nearly everything an agent needs to invoke it correctly, including the meaning of 'sub' and any privilege requirements.

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 0% across 4 parameters, so the description must compensate and does not. The 'user' and 'group' values are only faintly implied by 'owner', and the boolean 'sub' parameter (evidently recursive application) is left completely unexplained, as is the expected format of 'path'.

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 states a specific verb and resource ('Change file owner'), which is semantically clear on its own. However, it offers no scope or differentiation from the closely related sibling chmod_file (permissions vs. ownership), so an agent must infer the distinction from the tool names alone.

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?

There is no when-to-use guidance, no mention of prerequisites (ownership changes typically require elevated privileges/root), and no reference to alternatives such as chmod_file or move_file. The agent gets no routing help.

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