write_python_file

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

No annotations provided, so description carries full burden. It describes mutation ('write') but fails to disclose error handling (e.g., behavior when file exists and overwrite=False), permission requirements for 'system-wide', or side effects. The return value is not described.

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: one-sentence purpose followed by a clearly formatted parameter list. No extraneous information, and the key action is 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?

Covers basic purpose and parameters but lacks error handling info, sibling differentiation, and behavioral details. Given no output schema or annotations, completeness is adequate but not thorough.

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%, so description partially compensates with 'Args:' section offering basic parameter descriptions (path, content, overwrite). These add minimal meaning beyond schema names but lack depth, such as format constraints or examples.

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 verb 'write' and resource 'Python file', and mentions scope (working directory or system-wide). It distinguishes from sibling 'write_file' by specifying 'Python', but doesn't explicitly contrast with other siblings like 'run_python_file'.

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 tool versus alternatives (e.g., 'write_file' for non-Python files, 'run_python_file' for execution). The description only lists parameters without usage context or prerequisites.

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