settle_single

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

With no annotations, the description carries the full burden. It discloses floor rounding and integer-cent output, which are useful behavioral traits. However, it fails to specify how push/void outcomes are handled (e.g., stake returned, zero profit) or the profit formula, leaving ambiguity for edge cases.

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 a single, front-loaded sentence that conveys the core purpose with no unnecessary words. Every element contributes to understanding.

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?

There is no output schema, so the description must explain the return format and per-outcome behavior. It only states 'return and profit in integer cents' without indicating whether the output is a tuple, object, or how push/void map to outputs, making the tool difficult to invoke 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 only 33%, with only decimalOdds described. The tool description adds no parameter-specific meaning beyond what is already apparent from the schema (e.g., stakeCents is in cents, result enum). It does not explain how the parameters relate to the computed return and profit.

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 computes return and profit in integer cents for a single bet with floor rounding. The verb 'return' and resource 'single bet' distinguish it from sibling tools like settle_accumulator and settle_each_way.

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 phrase 'single bet' implies the tool is for single-bet settlement, giving some context. However, it does not explicitly contrast with alternatives like settle_accumulator or settle_each_way, nor does it provide when-not-to-use guidance.

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