content_read

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

The readOnlyHint annotation already covers the safety profile. The description adds useful behavioral context by explaining that unit_status reflects transfer status and expected_revision compares against the current body of the same source entry. Still, it leaves other behavioral aspects such as versioning, budget limits, and scope handling unexplained.

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 short and contains no filler, but it is under-specified rather than concise. It lacks structure, examples, or parameter context, making it less useful than its brevity suggests.

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 tool with six parameters, no schema parameter descriptions, and many sibling content/document tools, this description is incomplete. It does not clarify the notion of a unit, explain the other parameters, or situate the tool among its siblings. The readOnly annotation and output schema reduce but do not eliminate the need for more context.

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?

With schema description coverage at 0%, the description needed to explain the six parameters. It only touches expected_revision and leaves ref, scope, budget, version, and resource without meaningful explanation. This is insufficient compensation for the schema gap.

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 clear verb and resource: read a complete unit. It also introduces two relevant concepts, unit_status and expected_revision. However, it does not define what a 'unit' is or differentiate this tool from siblings like content_continue or content_snapshot.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling tool might be a better alternative. The expected_revision hint suggests a conditional use case, but it is not framed as usage guidance.

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