Read the mutation journal

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

With readOnlyHint and idempotentHint already present, the description still adds meaningful behavioral context: owner-only authorization, stable results, exclusion of raw arguments, links, and tokens, and the important caveat that a started entry without completion means the outcome is unknown. This goes beyond the annotations without contradicting them.

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 two compact clauses with no wasted words. The key properties are front-loaded, and the incomplete-entry caveat is stated directly and efficiently.

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 zero-parameter read tool with annotations and an output schema, the description covers authorization, result stability, content exclusions, and how to interpret incomplete entries. It does not clarify routing relative to similar log-oriented siblings, but the structured fields otherwise make it sufficiently 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?

The tool takes zero parameters, so there are no parameter semantics to describe. Per the evaluation baseline for zero-parameter tools, a 4 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?

The description identifies a specific resource and scope: an owner-only durable mutation journal. However, it phrases this as a noun fragment rather than an explicit verb, and it does not directly distinguish the tool from siblings like logs or access_log. The title supplies the missing verb, but the description alone is clear rather than fully self-contained.

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 'owner-only' constraint and 'mutation journal' resource imply the tool is for owners auditing mutations, but there is no explicit when-to-use guidance or named alternative among siblings such as access_log or logs. Usage is left to inference from the resource scope.

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