spraay_free_estimate_batch

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

Annotations already mark readOnlyHint and openWorldHint. The description adds behavioral context: it's a 'rough' batch estimate, 'free', and 'no live quote', plus explains how to pass parameters. No contradictions with 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?

Three concise sentences with no redundancy: first covers purpose and nature, second cost and read-only, third usage instructions. Every sentence adds value.

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 the simple tool with one parameter, full schema coverage, and existing annotations plus output schema, the description adequately covers purpose, behavior, and usage. No missing essential information.

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?

The sole parameter 'params' is fully described in the schema (100% coverage). The description only reiterates 'Pass any query parameters as a JSON string via the params argument', adding little meaning beyond the schema's existing description.

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 clearly states the tool provides a 'Rough batch cost estimate (no live quote)', identifying its purpose as a cost estimation tool for batch operations. However, it does not explicitly differentiate from sibling tools like spraay_compute_estimate or spraay_batch_estimate, though 'Free to call' hints at a distinction.

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?

It mentions 'no live quote' and 'Free to call. Read-only.', which implies it is suitable for rough, cost-free estimates. However, it doesn't provide explicit when-to-use or when-not-to-use guidance, nor mention alternative tools for live quotes or more accurate estimates.

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