journal_append

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation profile is covered structurally. The description adds only the "today's" scoping; it says nothing about whether entries can be edited/deleted, ordering guarantees, or any auth requirement, so it barely adds value beyond annotations.

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 compact sentences, front-loaded with the core action and the journal path, then the kind vocabulary. Every clause earns its place with no filler.

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 three-required-parameter mutation tool with no output schema and 0% schema description coverage, the description covers the destination and the kind vocabulary but omits any guidance on title/body content and on what the append returns or how conflicts are handled. Just adequate, not complete.

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% and there are no enums defined in the schema, so the description's inline list of kind values (decision|observation|recommendation|proposal|review|retro|owner|system) is genuinely valuable and would otherwise be inaccessible. It does not, however, explain the role or expected content of the required title and body parameters, leaving partial compensation only.

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?

States a specific verb (Append) and resource (today's decision journal, memory/journal), which is clear and actionable. It does not differentiate from siblings like record_review or record_owner_decision, so the agent has to infer the boundary, but the core purpose is unambiguous.

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 "today's decision journal" implies the temporal scope and the kind enumeration implies what sort of entries belong here, so usage is implied. However there is no explicit when-to-use vs when-not guidance, nor any comparison to the sibling recording tools (record_review, record_owner_decision).

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