marm_log_entry

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

With no annotations, the description fully discloses behavioral traits: entries stored with date, topic, summary; ability to switch sessions via prefixed entries; optional date prefix; and return values (status, message, entry_id). No contradictions.

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 well-structured with bullet points, clear sections for entry format and parameters. Every sentence adds value, and it is concise without being overly terse.

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 covers input (entry and session_name), behavior (session switching, date tagging), and output (status, message, entry_id), which matches the existence of an output schema. It is complete for the tool's complexity.

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%, so the description adds significant meaning: for 'entry', it explains format and special prefixes; for 'session_name', it clarifies optional override. This fully compensates for the lack of schema descriptions.

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's purpose: 'Write a log entry to the active session.' It specifies the verb 'write' and resource 'log entry' in the context of an active session, distinguishing it from sibling tools like marm_delete or marm_log_show.

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 explains when to use the tool (to log entries) and provides details on entry format and session switching. It implicitly differentiates from siblings. However, it lacks explicit statements about when not to use this tool or alternative tools.

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