spraay_robots_deregister

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

The description says 'Remove Robot', implying a destructive action, but annotations set destructiveHint to false. This is a contradiction. Additionally, no behavioral traits (e.g., irreversibility, needed permissions) are disclosed beyond the annotations.

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 concise at three sentences and front-loaded with the main action. However, it is too brief, missing important details about the action's effects and usage.

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?

For a mutation tool with no annotations explaining side effects, the description is insufficient. It lacks details on what happens upon deregistration, error conditions, or response format even though an output schema exists. The tool's context among siblings is not leveraged.

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?

Input schema has 1 parameter (body) with 100% coverage. The description says 'Pass the request payload as a JSON string via the body argument', which merely restates the schema's description ('JSON request body'), adding no new meaning. Baseline of 3 is appropriate.

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 'Remove Robot (RTP)', which is a specific verb and resource. Among siblings like spraay_robots_register or spraay_robots_update, this tool's purpose is distinct. However, 'RTP' is unexplained, slightly reducing clarity.

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 alternatives (e.g., spraay_robots_update). No prerequisites, user roles, or context cues are provided. The description only says 'Free to call' and how to pass the payload.

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