create_folderCreates a resume folder and returns its ID; if a folder with the exact title already exists, returns that folder instead.
Create a new resume folder and return its id. If a folder with this exact title exists, returns it instead.
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes |
Changes observed during successful MCP inspections.
v0.3.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare non-readonly, idempotent, non-destructive, open-world behavior. The description adds useful detail beyond annotations by stating that it returns the id and that an exact-title duplicate yields the existing folder rather than an error.
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?
Two short sentences with no waste. The primary action and return value are front-loaded, followed immediately by the important duplicate-handling rule.
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 one-parameter create tool with no output schema, the description covers the action, return value, and duplicate behavior. It could still say more about title requirements or authorization, but the essential calling information is present.
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 single parameter has 0% schema description coverage, so the description must carry meaning. It does clarify that the title is matched exactly for duplicate detection, but it does not explain title constraints, formatting, or validation rules.
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?
Specific verb and resource: 'Create a new resume folder' plus the return value ('return its id'). It also distinguishes behavior from siblings that list or assign folders by explaining duplicate-title handling.
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 create intent is clear, and the duplicate-title rule implies when reuse occurs. However, it does not explicitly say when to call this versus list_folders or set_applicant_folders, nor does it state any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.