fibonacci_record

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

No annotations provided. The description only states the action but does not disclose that the tool likely requires a prior initialized session (fibonacci_init) or that it updates internal state. Behavioral traits like state dependency are missing.

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, no wasted words. Could be slightly improved by including context like 'for the Fibonacci system' or 'requires prior initialization', but remains concise.

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?

No output schema, no annotations, and the description omits important context: the tool likely requires an initialized Fibonacci session (fibonacci_init), and it does not explain how the next bet amount is returned (likely via output). Incomplete for a stateful betting tool.

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 coverage is 100% with a descriptive enum. The description paraphrases the enum values ('win or loss') but does not add new meaning beyond the schema. Baseline of 3 is appropriate.

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 action 'Record a bet result' and the output 'get the next bet amount'. It is specific to win/loss results, which matches the enum. The sibling context clarifies it belongs to the Fibonacci system, though the description itself does not mention Fibonacci.

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 guidance on when to use this tool versus other bet recording tools (e.g., martingale_record, dalembert_record). No mention of prerequisites like initialization.

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