kelly_init

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

No annotations are provided, so the description carries full burden. It does not disclose potential side effects (e.g., overwriting an existing session), authorization needs, or any destructive behavior. For an initialization tool, this lack of transparency is a gap.

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 redundant words, directly states purpose and listed parameters. Every word earns its place.

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 is provided, but the description does not mention return values (e.g., session object or success status). For a non-trivial initialization tool with 6 parameters, this omission leaves the agent uncertain about the response.

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 100%, so baseline is 3. The description lists the parameters but adds no new meaning beyond the schema (e.g., 'optional fractional Kelly' is already documented in the schema). It does not explain edge cases or parameter relationships.

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 'Initialize a new Kelly Criterion betting session' with specific parameters (bankroll, win probability, payout odds, fractional Kelly). This explicitly identifies the verb (initialize) and resource (betting session), distinguishing it from sibling tools like kelly_record and kelly_reset.

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 description implies usage for starting a new session, and sibling tool names (e.g., kelly_record, kelly_reset) provide clear alternatives for different actions. However, it does not explicitly state when not to use it or compare to other betting strategies.

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