spraay_compute_batch

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

Adds cost and discount details beyond annotations, but does not disclose return value (output schema exists), atomicity, or failure modes. Annotations (openWorldHint, readOnlyHint=false) are not contradicted.

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 key info (batch size, discount, mix types, cost). 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?

Covers core purpose and payment, but lacks workflow details (e.g., submission returns job IDs, execution status). Output schema may fill gaps, but description could be more complete.

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%, and description only repeats job types and count already in schema. No additional meaning provided beyond what schema offers.

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 clearly states verb 'submit' and resource 'batch compute jobs', specifies scope (up to 50 jobs, mixed types), and differentiates from sibling single-job compute tools.

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?

Mentions cost savings and discount, implying use for batching multiple jobs. Does not explicitly state when not to use but sibling context provides alternatives. Clear but not exhaustive.

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