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

With no annotations, the description carries the burden of disclosure. It clearly states that the operation overwrites the total content, which is a key behavioral trait. However, it does not mention prerequisites (e.g., document must exist), reversibility, permissions, or error behavior.

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 a single sentence that is front-loaded and to the point. It does not waste words, though 'overwrites or updates' is slightly redundant; 'overwrites' alone would be more direct. Overall, it is concise and readable.

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 simple two-parameter mutation tool, the description conveys the core effect (full content replacement), but lacks information about return values, error conditions, and whether the document must already exist. Since there is no output schema, the description should have provided some of this context to be fully 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?

Schema coverage is 100% for both parameters, so the schema already describes doc_id and content adequately. The description adds no additional parameter semantics beyond the schema; it repeats the notion of 'total content' which matches the content parameter.

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 uses a specific verb ('overwrites or updates') and identifies the resource ('a document's total content'), making it clear this is a write operation. It distinguishes from the sibling tool mcp_read_document by focusing on modification rather than reading.

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 usage (to modify a document's content) but does not explicitly state when to use this over mcp_read_document or mention any exclusions. The sibling tool name provides context, but the description itself offers no direct guidance on selection.

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

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

No annotations are provided, so the description carries the full burden. The verb 'reads' implies non-destructive behavior, but the description does not explicitly state that it is read-only, nor does it mention error handling, permissions, or output formatting. This leaves significant behavioral ambiguity.

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 a single, clear sentence with no filler words. It is front-loaded with the action and outcome, making it easy to scan. No unnecessary information is present.

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?

With no annotations and no output schema, the description should clarify what 'contents' means (e.g., plain text, JSON) and what happens for invalid doc_id. These gaps leave the agent uncertain about the return format and error conditions, making the description incomplete for a reliable invocation.

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 only parameter, doc_id, is fully documented in the schema with a clear description ('The ID of the document to read'). The tool description does not add any extra meaning beyond referring to the document, which meets the baseline for high schema coverage.

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 uses a specific verb ('reads') and resource ('document'), and states the outcome ('returns its contents'). This clearly distinguishes it from the sibling tool mcp_edit_document, which is for modifications.

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 usage for retrieving document contents, but it does not explicitly state when to prefer this over mcp_edit_document or any exclusion criteria. No alternatives are mentioned, so the agent must infer from the sibling name.

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