import_resume

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

With no annotations provided, the description carries the transparency burden. It discloses the key encoding requirement ('File content must be base64-encoded') and the conversion behavior, but it does not mention whether this creates a new record, overwrites existing data, or what the return value is.

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 two short sentences with no filler. It front-loads the main action and formats, then adds the essential base64 constraint. Every word contributes utility.

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 import tool with no output schema and no annotations, the description covers the input requirements, supported formats, encoding, and conversion target. It doesn't explain return values or side effects, but the tool's low complexity makes this a minor 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%, so the baseline is 3. The description adds value beyond the schema by listing accepted file types (PDF, DOCX, TXT, MD) and explicitly naming the output format (resmarkup), tying both parameters into a meaningful operational context.

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 ('Import'), a specific resource ('resume file'), and the conversion target ('resmarkup format'). It also lists supported file extensions, clearly distinguishing this tool from siblings like create_resume or update_resume.

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 implies when to use this tool: when a resume exists as a file in PDF, DOCX, TXT, or MD format. It does not explicitly mention alternatives or when not to use it, but the import vs. create/update distinction is reasonably clear from the tool name and description.

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