spraay_robots_update

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

Annotations already indicate non-readOnly, non-idempotent, and non-destructive. The description adds 'Free to call' which implies no cost, but does not elaborate on side effects, authorization needs, or update semantics beyond what annotations imply.

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?

Two sentences, front-loaded with purpose ('Update Robot'), immediately followed by cost and invocation instructions. No unnecessary words.

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?

Despite simple schema and output schema presence, the description lacks key context: what 'RTP' stands for, what fields can be updated, and any behavioral implications. This may lead to incorrect tool selection or invocation.

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 has 100% description coverage for the single 'body' parameter. The description restates it as 'request payload', adding minimal context. Baseline 3 is appropriate since schema covers meaning.

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 tool name 'spraay_robots_update' and description 'Update Robot (RTP)' clearly indicate the action (update) and resource (robot). However, it does not differentiate from sibling tools like spraay_robots_complete or spraay_robots_register, and the acronym 'RTP' is unexplained.

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 only states 'Free to call' and how to pass the payload, but provides no guidance on when to use this tool versus alternative robot tools, nor any prerequisites or when not to use it.

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