spraay_robots_task

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

Annotations already indicate readOnlyHint=false and idempotentHint=false, so the description's claim of 'Dispatch' aligns. The description adds the cost ($0.05 USDC), which is useful behavioral context. However, it does not discuss side effects, error conditions, or success/failure behavior beyond what annotations provide.

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 three sentences, efficient and front-loaded with the core purpose. It could be slightly improved by ordering information more logically, but it is already concise and to the point.

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 presence of an output schema, the description need not explain return values, but it lacks context about valid task values, the structure of the parameters object, required permissions, or rate limits. The cost is mentioned, but overall, the description leaves gaps in understanding tool usage.

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 coverage is 100% but descriptions are minimal ('task parameter', 'robot_id parameter'). The description adds only 'Provide the listed fields as typed arguments', which does not enhance understanding of parameter meaning or expected values. Baseline is 3 given high schema coverage.

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 'Dispatch robot task (RTP)', specifying the exact action and resource. The name 'spraay_robots_task' distinguishes it from sibling tools like spraay_robots_complete or spraay_robots_register, which handle different robot operations.

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?

The description mentions cost but provides no explicit guidance on when to use this tool versus alternatives like spraay_robots_complete or spraay_robots_update. The usage is implied by the purpose, but there is no when-to-use or when-not-to-use information.

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