append_fleeting

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

The description reveals the timestamping and file location, but with no annotations, the burden is on the description to disclose mutation behavior (appending is a write), file creation if missing, or formatting details. It doesn't mention reversibility, permissions, or effects on existing content.

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 fluff, and the core action is front-loaded. A slight improvement would be specifying whether the block is appended as a markdown bullet or heading.

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?

The description is minimal for a tool that mutates a file. It lacks details on file creation, error behavior, or return value, and no annotations exist to fill the gap. The simplicity of the tool mitigates this somewhat, but an agent needs more behavioral context.

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 coverage is 0%, but the single parameter 'content' is trivially inferable from the description ('append a timestamped block' implies content is the block text). The description gives no additional format or length constraints, but with one obvious parameter, this is adequate.

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 appends a timestamped block to a dated file in a specific directory, identifying the resource and action. It distinguishes from siblings by implying a low-friction capture path, though it doesn't explicitly name an alternative.

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?

The phrase 'Lowest-friction capture' implies this is for quick note-taking, but it doesn't explicitly state when to use it vs. alternatives like create_note or update_note. No exclusions or alternative tool names are given.

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