ptero_app_delete_servers_server_databases_database

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

No annotations are present, and the description fails to disclose behavioral traits such as whether the operation is destructive, idempotent, or requires specific permissions. The agent has no information about side effects or error conditions.

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 (one phrase), but it is not concise in a helpful sense—it provides minimal information. A single sentence that adds no context is under-specified rather than concise.

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 four parameters, no output schema, and no annotations, the description is grossly incomplete. It fails to explain what the tool does beyond the obvious, how parameters relate, or what the response looks like. For a delete operation, the agent needs to know if it is reversible or what data is affected.

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 the meaning or usage of the parameters (server, database, query, body). The format constraints (server and database can be string or integer) are only in the schema, not described.

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 'DELETE /api/application/servers/{server}/databases/{database}' restates the HTTP method and path, which is essentially a tautology of the tool's name. It conveys the action (delete) and resource (server database) but adds no value beyond the name.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., other delete tools) or any prerequisites (e.g., server must exist, database must exist).

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