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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false, which for an export is not self-explanatory; the description adds genuinely useful context by disclosing that the output is file content and that it may be truncated when very large. The "PRO" marker also hints that the call is gated or credit-consuming, which the agent would otherwise not know. It doesn't explain the cost or what happens when the CV lacks Europass-relevant fields, so it is not fully transparent.

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 short sentences with the action and the use case front-loaded and no filler. The standalone "PRO." fragment is terse to the point of being cryptic out of context, a minor structural blemish.

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, and the description covers the return shape (file content, possibly truncated) as well as the triggering scenario, which is what an agent needs to call it correctly. Adding what PRO gating or credit consumption implies would close the remaining gap.

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 100%, and the schema already documents cvId (with a pointer to list_my_takemeup_cvs), the format enum and the locale default. The description adds nothing about parameters, which is acceptable at this coverage level but is baseline only.

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 states a specific verb (export), resource (one of the user's CVs) and target format (EU Europass XML/JSON-LD), plus the reason (EU job portals). The format name alone distinguishes it from the sibling export_takemeup_cv_yaml, so an agent can pick correctly without opening the 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?

"Use when an application asks for an Europass CV" gives a concrete triggering condition. It stops short of naming alternatives such as export_takemeup_cv_yaml or export_my_takemeup_data, so the agent gets a positive trigger but no explicit routing rules.

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