execution_journal_log

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states the side effect (append), the prerequisite (active journal path from execution_journal_start), and the return format (JSON string with StructuredResult and updated stats). This is more transparent than typical MCP descriptions, though it does not mention failure modes or idempotency.

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 appropriately sized for a tool with 11 parameters: a one-sentence purpose, a compact argument list, a returns line, a KB pointer, and one example. Information is front-loaded and every component contributes to usability.

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 all parameters, the return type, an example invocation, and a KB reference for deeper detail. It lacks explicit preconditions (beyond the journal_path dependency) and error-handling notes, but given the output schema exists and the KB reference, it is nearly complete for calling the tool successfully.

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?

Every parameter in the schema is repeated in the description with a semantic explanation, fully compensating for the 0% schema description coverage. The relationship between journal_path and execution_journal_start is clarified, and optional fields are labeled. This exceeds the baseline because the description adds meaning beyond the raw type definitions.

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 opens with a specific verb and resource: 'Append a structured entry to an execution journal.' This clearly distinguishes it from journal lifecycle tools like execution_journal_start/finish and from other unrelated tools. The agent knows exactly what the tool does without inspecting the schema.

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 by stating that journal_path must be a value returned by execution_journal_start, which establishes a dependency and a sequence. However, it does not explicitly say when to use this tool versus execution_journal_finish, nor does it note any exclusions or alternatives. The KB link hints at context, but the guidance remains implicit rather than explicit.

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