Estimate generation cost

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states that the tool does not charge anything and returns the token cost and balance. It also discloses the critical constraint that the params must match deepy_create_generation (quote == charge). However, it does not mention error handling, side effects beyond charging, or rate-limit implications, so a small gap remains.

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?

The description is three sentences, each with a clear purpose: what the tool does, when to use it, and the critical constraint. There is no wasted wording, and the most important information is front-loaded in the first sentence.

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?

The tool is relatively simple, and the description covers its purpose, return value (integer token cost and resulting balance), and the no-charge behavior. It also provides workflow guidance. While there is no output schema, the description sufficiently explains what to expect. Minor omissions like error cases or balance ownership prevent a perfect score.

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 input schema already provides 100% coverage with detailed descriptions for each parameter, so the baseline is 3. The description adds meaningful cross-tool semantics by emphasizing that the exact same params must be passed to deepy_create_generation. This generalizes the schema's note about prompt text to all parameters, thereby enriching the understanding of how these parameters are used.

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's purpose: to get the integer token cost and resulting balance for a generation without charging. The verb 'Get' and the specific resource 'token cost and resulting balance' make it unambiguous. It also distinguishes itself from the sibling tool deepy_create_generation by explicitly stating it does not charge.

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?

The tool provides explicit usage guidance: 'Always estimate and confirm with the user before creating' tells the agent exactly when to invoke this tool. It further instructs that the same params must be passed to deepy_create_generation, defining the workflow between the two tools. This is clear, actionable, and differentiates the estimate step from the actual creation.

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