ptero_app_delete_nodes_node

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

With no annotations provided, the description carries the full burden. It only states the HTTP endpoint and says nothing about consequences (e.g., cascading deletions, permissions, irreversibility). The agent gains no behavioral insight beyond the tool name.

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 concise (one line) but at the expense of usefulness. It is front-loaded appropriately but lacks essential information, making it an underspecification rather than efficient conciseness.

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 3 parameters, no output schema, and no annotations, the description is severely lacking. It does not explain that this is an admin API call, how deletion affects related resources, or any error conditions. The agent has insufficient context to safely invoke the tool.

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%, meaning the parameter schema has no documentation. The description adds nothing about the required 'node' parameter (e.g., what it represents, format) or the optional 'query' and 'body' parameters. The agent must guess their purpose.

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 'DELETE /api/application/nodes/{node}', which essentially restates the HTTP method and path. It indicates deletion of a node resource but adds no additional context beyond what the tool name already conveys (delete_nodes_node). This is nearly a tautology.

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 is provided on when to use this tool versus alternatives, such as other deletion tools like ptero_app_delete_servers_server. There is no context about prerequisites, side effects, or scenarios.

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