upload_resume

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: file format constraints (PDF, DOC, DOCX), size limits (5MB), default behavior (profile syncing), and the effect of the isAltResume parameter. It doesn't mention authentication requirements, rate limits, or error conditions, but covers the essential operational constraints.

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 efficiently structured with four sentences that each serve a distinct purpose: stating the core function, listing constraints, providing implementation guidance, and explaining parameter behavior. There's no wasted text, and key information is front-loaded.

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 mutation tool with no annotations and no output schema, the description provides good coverage of operational constraints and parameter behavior. It could be more complete by mentioning authentication requirements, response format, or error handling, but given the schema's thorough parameter documentation, it's reasonably complete for the agent's needs.

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 schema already documents all parameters thoroughly. The description adds minimal parameter semantics beyond the schema - it mentions the purpose of 'isAltResume' and that 'syncProfile' is ignored for alt resumes, but doesn't provide additional context about parameter interactions or usage patterns.

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 clearly states the specific action ('Upload a resume as base64 file content') and distinguishes it from sibling tools like 'delete_resume' or 'get_resume' by focusing on file upload functionality. It specifies the resource (resume) and the method (base64 encoding).

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 provides clear context for when to use this tool (uploading resumes with specific formats and size limits) and mentions the 'isAltResume' parameter for alternative use cases. However, it doesn't explicitly state when NOT to use it or name specific alternatives among sibling tools like 'generate_resume_for_job' or 'import_job_by_url'.

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