write_file

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

Annotations already declare destructive and idempotent hints. Description adds 'Requires file-write access' and confirms overwrite behavior. However, it doesn't explain what happens to existing files beyond overwrite, whether directories are created, or any limits.

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?

Two sentences, no unnecessary words. Well-structured and front-loaded.

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 destructive, multi-parameter tool with no output schema and no parameter descriptions, this is insufficient. Missing return behavior, error handling, path interpretation, server_id usage, and differentiation from safe_write_file.

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 descriptions are 0% and the description adds no explanation of path, content, or server_id. Path and server_id semantics are ambiguous. The description provides no parameter guidance.

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?

Clearly states 'Create or overwrite a text file' with a specific verb and resource. However, it does not differentiate from sibling safe_write_file, which likely serves a similar purpose with extra safety checks.

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?

No guidance on when to use this vs alternatives. There is a 'safe_write_file' sibling that may be a safer alternative, but the description doesn't mention it. Only notes a permission prerequisite, not usage context.

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