spraay_robots_profile

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

Annotations already provide readOnlyHint and openWorldHint. Description adds cost info ($0.002 USDC per call), which is valuable. The rest ('Read-only', 'Pass the listed fields...') adds minimal behavioral context beyond 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?

Short and front-loaded with key info. Could be more structured (e.g., bullet points) but no excessive verbiage.

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?

Adequate for a simple read-only tool with one parameter and an output schema. Includes cost and read-only nature, though could mention typical usage or scope.

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 describes 'robot_id' as just 'robot_id parameter', a weak definition. Tool description adds no meaning, only instructing to pass fields directly. No clarification of what robot_id represents (e.g., unique identifier) or examples.

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?

Description states 'Robot profile' which implies fetching detailed info for a specific robot, and mentions 'Read-only'. It distinguishes from siblings like spraay_robots_list (list) and spraay_robots_status, but lacks a verb like 'Get' or 'Retrieve'.

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 vs alternatives. Mentions cost and read-only, but doesn't explain scenarios or compare to other robot tools.

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