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

Annotations only indicate that this is not read-only, so the description carries the burden of explaining side effects. It does so by disclosing that the default behavior saves the profile and rebuilds the job feed, and that save=false avoids persistence. It also adds practical constraints: PDF/DOCX formats and an 8 MB limit.

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?

Three dense sentences with no filler: purpose, parsed fields, save behavior, and size limit are all covered. The most important outcome is front-loaded, and the conditional branch is explained immediately after.

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?

The description covers accepted formats, size limit, parsed fields, and the persistence vs review-only behavior, which is sufficient for most calls. The main gap is that it does not explicitly state what a successful save=true response contains, but the absence of an output schema is partially mitigated by describing the resulting profile state.

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 schema documents filename and content_base64 and notes save's default, but the description adds meaningful semantics: save=true vs false changes whether the parser result is persisted or just returned, and file type/size constraints are called out. This supplements the schema rather than merely repeating 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 description names a specific verb and resource: it uploads a CV file and converts it into the account's profile. It also lists the parsed fields, making the tool's function concrete and distinct from read-oriented siblings like get_my_profile or preview_tailored_cv.

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 clearly explains the two modes of use: save=true saves the profile and builds the job feed, while save=false returns the parsed profile for review only. It does not explicitly name alternatives like update_profile or preview_tailored_cv, but the conditional behavior provides solid usage guidance.

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