mindbase_append_log

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

The description discloses a side effect: appending a structured entry to a daily log file, and the exact format used. However, with no annotations and no output schema, it does not say whether the file is created if missing, what the return behavior is, or how projectId affects which log file is used.

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 concise and front-loaded: one clear sentence states the action and target, followed immediately by the required entry format. No content is wasted.

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 append operation, the path and format give enough to make a basic call successfully. Still, the lack of return information, explicit side-effect description, and usage distinction from nearby write/log tools leaves meaningful gaps.

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?

The schema already documents operation, details, and projectId meaning. The description adds value by showing how parameters map into the final log line, but it does not fully explain topic semantics or the interaction of projectId with the file path.

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 ('append') and the target resource ('logs/<today>.md'), and it gives a concrete entry format. This makes the tool's purpose easy to grasp and distinguishes it from write tools like append_to_page or create_daily_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 does not say when this tool should be used, nor when to prefer another tool such as save_chat_excerpt, create_daily_note, or mindbase_contribute. The format implies operational logging, but no explicit context, prerequisites, or exclusions are given.

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