ptero_app_delete_servers_server

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

No annotations provided, and the description fails to disclose behavioral traits such as irreversibility, required permissions, side effects (e.g., associated resources deletion), or error conditions. For a destructive operation, this is a critical omission.

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?

Extremely brief (6 words), but it sacrifices completeness. Every word is the API path, providing no additional value. It is not well-structured or front-loaded with actionable 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 performs a delete operation, the description should cover return behavior, error scenarios, and dependencies. With no annotations, output schema, or parameter explanations, the description is wholly inadequate for an agent to use correctly.

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 does not explain any of the three parameters (server, query, body). The required 'server' parameter is not defined, and optional parameters are ignored. The agent gets no semantic help beyond schema types.

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 is a REST API path 'DELETE /api/application/servers/{server}', which implies deletion of a server, but it's essentially a tautology of the tool name and lacks a clear verb+resource explanation. It distinguishes from siblings only via the path.

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?

No guidance on when to use this tool versus other delete tools (e.g., ptero_app_delete_locations_location). The description provides no context, prerequisites, or exclusions.

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