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

With no annotations provided, the description carries the full burden. It adds one behavioral constraint (primary vs alternate), which is useful, but it does not disclose whether deletion is permanent, any side effects, or potential errors. The note about primary resumes is helpful, but more transparency (e.g., irreversibility) would be expected for a delete operation.

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 a single concise sentence plus a brief note. Every word earns its place, and the key limitation is front-loaded. There is no fluff or repetition of schema information.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential purpose and a critical usage restriction. It could mention the result or error behavior, but for a straightforward delete operation with the given context, it is reasonably complete.

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 schema already describes the 'id' parameter as 'The resume ID (URI) to delete' with 100% coverage. The description adds meaning by implying the ID must be an alternate resume, not the primary one, which is a valuable constraint beyond the schema. Therefore it earns a 4, above the baseline of 3.

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 an uploaded resume from your profile.' It uses a specific verb and resource, and the additional note about primary vs alternate resumes clarifies the tool's scope, distinguishing it from resume upload/list/get tools.

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 gives explicit when-not guidance: 'You cannot delete your primary resume, only alternate resumes.' This tells users the tool is for alternate resumes only, providing clear context. However, it does not explicitly name alternative tools for deleting a primary resume, so it falls short of a 5.

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