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

Goes well past the annotations by disclosing refusal rules (LinkedIn, private-network URLs, redirects), a size/MB ceiling, the asynchronous background-parse lifecycle with status 'parsing' and a ~1 minute wait, the merge behavior ('preserves existing stated profile fields', pasted text never replaces an uploaded PDF), and a prompt-injection warning that resume text is untrusted data. None of that is recoverable from readOnlyHint/destructiveHint/openWorldHint alone.

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?

Six sentences, each carrying distinct payload (modes, exclusivity, refusals, parity with web flow, preservation rule, security note, async protocol), with the core action front-loaded. Slightly dense but no sentence is filler.

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?

An output schema exists, so the description is not obliged to describe return values, yet it still characterizes the async result (roles, years, skills, profile completeness). With annotations, full schema coverage, and an output schema all present, nothing an agent needs to invoke this correctly is missing.

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%, so the baseline is 3; the description earns more by adding constraints the schema cannot express — that the three inputs are mutually exclusive and that cv_upload_id is used *alone* on a re-call rather than combined with the original input.

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 states a specific verb and resource with quantified scope ('Parse the member's pasted resume text or fetch one direct public HTTPS PDF up to 10 MB'), and the dual-mode nature (submit vs read-back) is spelled out. An agent can distinguish this from tailor_resume or update_profile without opening any schema.

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?

Gives an explicit selection rule among inputs ('Supply exactly one of text, pdf_url or cv_upload_id') and an explicit follow-up protocol ('call again with only that cv_upload_id in about a minute'). It does not, however, contrast this tool with adjacent siblings like update_profile or tailor_resume, so the routing is clear but not fully closed.

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