theta_estimate_cost

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

Clearly states 'pure calculation, no API calls' indicating no side effects or external dependencies. With no annotations provided, this description effectively communicates the tool's safe, read-only behavior.

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?

Single sentence front-loading purpose and key behavioral trait. Every word adds value, no redundancy.

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?

Despite low complexity, the description omits parameter details and any mention of return values. For a cost estimation tool, users need to know what the output is (e.g., a number in TFUEL) to use it correctly.

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 description coverage is 0%, but description adds no explanation for 'model' or 'duration_minutes'. These parameter names are somewhat self-explanatory, but the tool's utility hinges on knowing valid model values, which is absent.

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 the tool estimates TFUEL cost for a GPU job, with a specific verb ('estimate') and resource ('cost'). It is distinct from all sibling tools, none of which do cost estimation.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'pure calculation, no API calls' implies safety and speed, but does not give context like 'use before submitting a job' or alternatives.

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