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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions the auth requirement, which is a key constraint, but it does not disclose whether the deletion is irreversible, what side effects occur on associated data, or any error conditions. The destructive nature is implied by 'delete' but not elaborated.

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 very short and front-loaded with the primary purpose. The second sentence adds a necessary constraint. The dash between the sentences is slightly awkward but does not detract much from clarity. Overall, it is concise and to the point.

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 is a destructive delete operation with no output schema and no annotations, the description is incomplete. It lacks information on return values, error handling, permissions beyond the logged-in constraint, and how it relates to other user-management tools. The description only covers the bare minimum.

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%, and the description offers no explanation of the parameters. 'username' is somewhat self-explanatory, but 'x-hapi-auth-state' is cryptic. The description does not clarify whether 'username' must refer to the logged-in user or any user, nor does it explain the auth state parameter format. This is a significant gap.

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 tool deletes a user resource ('Delete user resource'), which distinguishes it from siblings like createUser, updateUser, and getUserByName. The additional constraint about the logged-in user adds specificity without ambiguity.

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 provides a usage condition: 'This can only be done by the logged in user.' This implies the agent should only invoke the tool when the user is authenticated. However, it does not explicitly mention when not to use it or compare it to alternatives like updateUser or deletePet.

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