capture_journal

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal a write operation ('create or append') and a light-editing philosophy, which is genuine behavioral context. However, it does not disclose how the tool decides append vs. create, whether it is idempotent, auth requirements, or what it returns — gaps that matter for a write tool with zero annotation coverage.

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 tight sentences with no filler. The purpose is front-loaded in the first sentence, and the second sentence carries the only substantive addition (editing guidance). Every word 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 4-parameter write tool with no annotations and no output schema, the description is thin but the schema is fully self-documenting. The main gaps are the append-vs-create decision logic and the missing differentiation from capture_input in the sibling set, neither of which the schema can compensate for.

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 100%, so the baseline is 3 even without parameter detail in the description. The description reinforces the content parameter's meaning via 'lightly edited content,' but adds nothing about keyword-as-filename, date defaults, or title that the schema already explains. It does not exceed the baseline.

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 states a specific verb and resource: 'Create or append a personal journal fragment.' This clearly separates it from the read-oriented siblings get_records_by_date_range and search_records. However, it does not distinguish itself from the near-namesake capture_input, leaving the agent to guess how journal capture differs from general input capture.

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 instruction to 'Supply lightly edited content that preserves the user's words and uncertainty' provides useful guidance on how to phrase the content body. But there is no when-to-use guidance versus capture_input, and no conditions under which one should be preferred over the other, so an agent selecting between the two capture tools gets no help.

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