delete_resume

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

No annotations are provided, so the description carries the full burden. It discloses a key behavioral constraint (cannot delete primary resumes), which is crucial for a destructive operation. However, it lacks details on permissions, error handling, or confirmation steps, leaving gaps in behavioral understanding for a deletion tool.

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 sentences, front-loaded with the core action and resource, followed by a critical constraint. Every word serves a purpose, with no redundancy or fluff, making it highly efficient and well-structured.

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 destructive tool with no annotations and no output schema, the description provides essential context (cannot delete primary resumes) but lacks details on outcomes (e.g., confirmation message, error responses) or broader implications. It's adequate given the simple parameter schema but could be more complete for a mutation operation.

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%, with the parameter 'id' fully documented in the schema. The description does not add any additional semantic context beyond what the schema provides (e.g., format examples or source of the ID), so it meets the baseline for high schema coverage without extra value.

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 action ('Delete') and resource ('an uploaded resume from your profile'), distinguishing it from sibling tools like 'upload_resume' or 'get_resume'. It specifies the scope of deletion (only alternate resumes, not primary), making the purpose explicit and differentiated.

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 explicitly states when not to use this tool ('You cannot delete your primary resume'), providing clear exclusion criteria. It implies usage for deleting alternate resumes, and while it doesn't name alternatives directly, the context from sibling tools (e.g., 'upload_resume', 'list_resumes') supports understanding of when to use it.

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