spraay_compute_models

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

Discloses that the tool is free and read-only (via annotations), adding cost and safety context. The grouping behavior is described, providing clarity beyond the readOnlyHint annotation.

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 concise sentences with key information front-loaded: listing, pricing, grouping, and cost. No wasted 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?

Given an output schema exists, the description covers purpose, output organization, and cost. It does not mention pagination or freshness, but for a simple list endpoint, it is adequate.

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?

No parameters exist, and schema coverage is 100%. Description adds no parameter-level detail since none are needed; baseline 3 applies due to high 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?

Clearly states it lists all available compute models with pricing and capabilities, grouped by type. Distinguishes from sibling tools like spraay_gpu_models or spraay_bittensor_models by noting free access and comprehensive grouping.

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?

Explicitly mentions 'FREE — no x402 payment required,' indicating low-cost or free usage. However, lacks explicit comparison to alternative model-listing tools or guidance on when to use this versus other sibling tools.

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