fibonacci_statistics

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

No annotations provided, so description carries full burden. It does not disclose side effects, error conditions (e.g., uninitialized session), authentication needs, or rate limits. The agent cannot infer whether this is a safe read or has potential pitfalls.

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, 15 words, no redundancy. Front-loaded with the purpose and key details. 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?

With no parameters and no output schema, the description should explain prerequisites (e.g., session must be initialized), return format, or edge cases. It only lists metrics, leaving the agent uninformed about session state dependency and response structure.

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?

Input schema has no parameters (0 params), baseline is 4. The description adds value by specifying the included statistics (win rate, ROI, streaks, risk metrics), which helps the agent understand what the tool returns without an output schema.

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 retrieves detailed statistics for the Fibonacci session, listing specific metrics (win rate, ROI, streaks, risk metrics). It distinguishes from sibling tools like fibonacci_init, fibonacci_record, fibonacci_reset, and fibonacci_status by focusing on statistics.

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 after session initialization and recording, but does not explicitly state when to use it versus alternatives (e.g., fibonacci_status) or provide exclusion criteria. No guidance on prerequisites or ordering.

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