log_to_note

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses the append action, the target section, the exact log entry format including a date and time, and the return behavior. It omits edge cases such as whether a missing note or missing 'Logs' section would be created, but the core behavior is well specified.

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 compact and well-structured, with the purpose stated first, followed by the format, arguments, and return value. There is no filler or redundant repetition, and each section earns its place.

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 simple two-parameter write tool, the description covers the main call path, arguments, format, and return value. However, it lacks edge-case behavior (missing note, missing section) and does not help an agent choose among the many sibling log/append tools, leaving some contextual ambiguity.

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%, but the description compensates by defining both parameters meaningfully: note_path is a path relative to the vault root, and content is the log message to append. The format line further clarifies how content will be rendered into the note.

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 action (append), the resource (log entry), and the destination (the 'Logs' section of any note), with an explicit format. It is unambiguous about what the tool does, though it does not explicitly differentiate itself from sibling tools like log_to_daily_note or append_to_note.

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 description implies usage context: logging into the 'Logs' section of a general note, including project or task notes. However, it gives no explicit guidance about when to use this tool instead of log_to_daily_note, append_to_note, or add_to_inbox, and does not mention any exclusions.

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