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

Annotations already establish readOnly, idempotent, non-destructive, non-open-world behavior, so the bar is lower. The description adds non-obvious context: resume text must be treated as untrusted data, hidden sections/entries are respected by default, and the result is not saved back to Bespree. One clause ('use this authorized content without calling or waiting for Bespree export tools') reads as workflow policy rather than tool behavior but does not contradict the 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 core purpose is front-loaded in the first sentence, which is good, but the remainder is a long run-on mixing security policy, export substitution rules, and UX instructions ('Explain that the file uses your own layout...'). Several sentences serve downstream formatting policy rather than helping an agent select or invoke this read tool.

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?

There is no output schema, so the description must describe returns, and it does list the returned artifacts (section/entry IDs, display controls, version, editor link). The main gap is that nothing explains the required resumeId, but for a single-parameter read tool with strong annotation coverage the definition is otherwise complete enough to call 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% for the single required resumeId parameter, so the description carries the full burden of explaining it and does not mention resumeId at all. The 24-hex-char pattern exists only in the schema with no prose meaning, leaving the agent no guidance on what identifier to supply or where to obtain it.

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 opening sentence names a specific verb and resource ('Read a selected resume') and enumerates what it returns: stable section/entry IDs, display controls, current version, and an editor link. That is enough to distinguish it from write siblings like update_resume or create_resume, though it never explicitly names the export tool it contrasts with, so it falls short of a 5.

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 gives real conditional guidance: use this content for independently formatted PDF/DOCX output without calling Bespree export tools, honor hidden sections unless requested otherwise, and never silently substitute for a requested export. It is clear about context but is written as policy advice rather than crisp when-to-use routing, and does not note conditions like permissions or version state.

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