add_journal_entry

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

Description only indicates creation (mutation), but lacks details on idempotency, duplicate handling, permission requirements, or what happens on success/failure. With no annotations, the description carries the burden but provides minimal behavioral context.

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?

One short sentence with no fluff, clearly conveying purpose. Could add structure but remains efficient.

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 creation tool with 9 parameters, no output schema, and no annotations, the description is too sparse. Missing details on constraints (e.g., date uniqueness), return value, and error handling.

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 has 100% description coverage for all 9 parameters, so the description adds limited semantic value beyond 'structured metadata'. Baseline 3 is appropriate.

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?

Clearly states the verb 'create', the resource 'daily journal entry', and hints at structured metadata, distinguishing it from sibling tools like search_journal or list_recent_journal_entries which are read-only.

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?

No guidance on when to use this tool versus alternatives (e.g., updating an existing entry or retrieving today's entry). No 'when not to use' or prerequisites provided.

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