goodman_statistics

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

With no annotations, the description carries the full burden. It describes the tool as retrieving statistics, implying a read-only operation. However, it does not confirm that no state is modified, nor does it specify prerequisites like an existing initialized session.

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, well-structured sentence that immediately states the action and resource, and provides specific examples. No unnecessary words.

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 has no parameters and no output schema, so the description must cover both input and output behavior. It clearly states the purpose and examples of output metrics. However, it does not describe the structure of the returned statistics or any dependencies (e.g., session must be active). Features like pagination or error cases are not mentioned, but are likely minimal for a statistics 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?

The tool has no parameters, and schema coverage is 100% (trivially). The description adds value by listing the types of statistics provided, which compensates for the lack of parameter documentation.

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 uses a specific verb 'Get' and identifies the resource 'detailed statistics for the current Goodman session', listing concrete metrics like win rate, ROI, streaks, and risk metrics. This clearly distinguishes it from sibling tools like goodman_init or goodman_record, and from statistics tools of other systems by naming the system and providing examples.

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 retrieving statistics after a session, but it offers no explicit guidance on when to use this tool versus alternatives like goodman_status or statistics tools for other systems. It does not state prerequisites or when not to use.

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