ptero_app_delete_users_user

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

No behavioral traits are disclosed beyond the HTTP DELETE method, which implies destructiveness. There is no mention of permissions, reversibility, side effects, or failure modes. Since no annotations are provided, the description carries the full burden but fails to deliver.

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 extremely short, but this is underspecification rather than conciseness. It does not provide enough information to be considered well-structured or useful.

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 destructive nature of the tool, lack of output schema, and three parameters, the description is grossly incomplete. It does not explain the result of deletion, error conditions, or any prerequisites.

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 description adds no meaning to the three input parameters. With 0% schema description coverage, the description should compensate, but it does not explain what 'user', 'query', or 'body' represent or how they should be used.

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 merely restates the HTTP method and endpoint, providing minimal indication that it deletes a user resource. It does not explain what action the tool performs or how it differs from sibling delete tools (e.g., delete server, delete location), only the endpoint differentiates them.

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?

There is no guidance on when to use this tool, prerequisites, or alternatives. The description gives no context for selection relative to other tools.

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