spraay_robots_list

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

Annotations already provide readOnlyHint and openWorldHint. The description adds cost ($0.005 per call) and an instruction on parameter passing. While useful, it lacks details like rate limits, authentication, pagination, or response structure. The description does not contradict 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 extremely concise: two sentences with no redundant words. It front-loads the core purpose ('Discover robots'), then adds cost, read-only status, and an instruction. Every sentence earns its place.

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 having an output schema (so return values need not be explained), the tool is a list operation with two optional filters. The description lacks information on how filters affect results, pagination, ordering, or limits. Sibling tools exist, but no context is provided for when to use this list vs other robot tools.

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 parameter descriptions are tautological ('max_price parameter'). The description says 'Pass the listed fields directly as typed arguments' but does not clarify what max_price or capability represent (e.g., unit, source). The description adds minimal semantic value beyond the schema.

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 states 'Discover robots' which gives a clear verb and resource. The name includes 'list', and sibling tools have distinct verbs (register, update, etc.), so the tool's purpose is distinguishable even without explicit differentiation.

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 says 'Read-only', implying it should be used for retrieval, not modification. No explicit exclusions or alternatives are mentioned. The sibling tools suggest alternatives (e.g., status, profile), but no guidance is provided.

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