append_file

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

Describes the basic action (append text) but lacks details on behavior beyond that. Does not disclose if the file is created if missing, any side effects, or permission requirements. No annotations provided to supplement.

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?

The description is a single short sentence, which is concise but at the expense of completeness. It is not verbose, but could usefully include more information without becoming overly long.

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 tool with no output schema, no annotations, and simple parameters, the description is insufficient. It omits return value, error cases, and behavior for missing files, which are important for an agent to use correctly.

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% and the description adds no meaning beyond parameter names. The two parameters (targetPath, content) remain opaque regarding format, restrictions, or expected values.

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 'Adiciona' (adds) and the resource 'texto ao final de um arquivo' (text to the end of a file). It distinguishes from siblings like write_file by implying append behavior, but does not explicitly contrast.

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 like write_file. No mention of prerequisites, such as whether the file must exist or will be created, or when to prefer append over overwrite.

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