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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description does not need to restate those. It adds a useful behavioral caution: "Preserve ^task markers when writing back," which tells the agent that journal content may contain markers that must survive round-trips. This goes beyond the structured 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?

The description is very concise and front-loaded with the core purpose. The additional warning about ^task markers is short and adds important behavioral context without unnecessary elaboration.

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 read operation with strong annotations, the description covers the basic action and warns about an important data quirk. However, there is no output schema, and the description does not explain what the response contains, how multiple dates are returned, or how the date parameter behaves. This leaves some gaps for an agent trying to use the tool correctly.

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 0%, and the description does not meaningfully explain the optional date parameter. The phrase "daily journal and recent dates" hints at date-based behavior but does not clarify the expected format, the effect of omitting the parameter, or the exact scope of "recent dates." The description fails to compensate for the missing schema documentation.

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 action and resource: "Read a daily journal and recent dates." This clearly identifies what the tool does and distinguishes it from sibling tools like write_journal. However, it does not explicitly differentiate from other get_* tools or clarify what "recent dates" means.

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 the tool is for reading journal content, and the readOnly annotation reinforces that. It does not explicitly say when to prefer it over alternatives, nor does it mention write_journal as the counterpart for modifications. Usage context is present but only implied.

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