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

There are no annotations, so the description carries the full burden. It does disclose one real behavioral trait — that associated resources are cleaned up — and notes auth is required, but it says nothing about irreversibility, whether confirmation is needed, which resources are removed, or what happens on partial failure.

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 core sentence is tight and front-loaded, but the boilerplate "### Responses: **200**: Successful Response / Content-Type: application/json" block adds no decision-relevant information and pads the definition.

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?

This is an irreversible mutation tool with no annotations, no output schema, and two undocumented parameters. The description covers only what it deletes and that auth is required; an agent still lacks enough to invoke it confidently or understand the blast radius.

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 0% for both parameters (s3Path, user_id), and the description never mentions either. The phrase "the user's resume" weakly implies user_id identifies whose resume, but s3Path is entirely unexplained in both schema and description.

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?

"Delete the user's resume and cleanup associated resources" gives a specific verb (delete) and resource (the user's resume), which distinguishes it from siblings like update_resume_manual or upload_resume. It stops short of naming any sibling outright, so it is clear but not maximally 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 never says when to use this instead of the alternatives (update_resume_manual, save_resume_yaml, delete_preferences) or under what preconditions deletion is appropriate. The only contextual statement is "Requires authentication," which is a prerequisite, not usage guidance.

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