swagger-petstore---openapi-3.0.deleteUser

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

The description merely restates the tool's name and offers no additional behavioral context beyond the destructiveHint annotation. It does not mention whether deletion is permanent, what data is removed, or any side effects.

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 one short sentence with no filler or repetition. It is perfectly concise for a simple delete operation and front-loads the action effectively.

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?

The description is too terse to explain how the user is identified, especially given an empty input schema, and it omits any prerequisites or consequences of deletion. An output schema exists, but core usage context is still missing.

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 tool has zero parameters and the input schema is fully described, so parameter explanation is not needed. The description adds no parameter semantics, but the baseline for a zero-parameter tool is strong.

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 explicitly states the verb 'Delete' and the resource 'user', doing exactly what the tool does. This disambiguates the tool from sibling operations such as createUser, updateUser, and deletePet.

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?

It implies the tool should be used when a user resource needs to be removed, but provides no explicit context, exclusions, or alternative tools. No guidance covers prerequisites like authentication or whether the user must already exist.

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