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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, closed-world, so the safety profile is covered. The description still adds real value beyond them by disclosing an output quirk: a saved job ad or imported text comes back under 'foreign', which an agent would not otherwise know.

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?

One dense sentence with the payload contents listed up front and the 'foreign' caveat trailing; no filler, no restatement of annotations or schema.

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 output schema, the description correctly compensates by enumerating return fields and flagging the foreign-content case. Missing only minor operational detail such as error behavior for an invalid or inaccessible resumeId.

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% and the single resumeId parameter is documented as 'A resume id from list_resumes', so the schema does the heavy lifting. The description adds no further semantics about the id format or sourcing, matching the baseline 3 for a fully-documented single param.

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?

Names the exact resource ('One resume') and enumerates its returned contents (contact, headline, summary, experience, education, skills, projects, certifications) plus template, colour and contentVersion, which unambiguously separates it from list_resumes and the mutation siblings. The verb is only implied via the title 'Read resume' rather than stated in the description itself.

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 phrase 'One resume's full content' implies the single-record vs. list distinction, but there is no explicit when-to-use guidance, no mention of pairing with list_resumes to obtain the id, and no statement of when not to use it (e.g., use get_account for account data).

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