get_cost_estimate

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

No annotations provided, so description carries full burden. It discloses that null costs are returned if rates not configured, and implies a read-only operation. For a simple tool, this is sufficient behavioral clarity.

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?

Description is three concise sentences plus a structured argument line. No wasted words; first sentence states purpose. Ideal length and front-loading.

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 tool with one parameter and no output schema. Covers purpose, parameter, edge case (null), and alternative. Could specify return format (e.g., currency) but not critical.

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 has 0% coverage, so description must compensate. It explains the 'hours' parameter as 'Look-back window in hours (default 24)', adding meaningful context beyond the schema's type and default.

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 'Return estimated GPU spend for the last N hours', specifying the verb (return), resource (GPU spend), and time window. It distinguishes from siblings like get_gpu_metrics by mentioning utilization data without cost.

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 states when to use (cost rates configured) and when not (returns null if no rates). Provides an alternative tool (get_gpu_metrics) for utilization data without cost. Also mentions prerequisite (set_cluster_rate).

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