get_session_stats

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

With no annotations provided, the description fully bears the burden of disclosing behavior. It accurately describes the tool as returning cumulative statistics (no side effects) and lists the returned data fields. This is complete and transparent for a read-only, zero-parameter tool.

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 two sentences with zero waste. The first sentence states the action and output; the second gives a usage recommendation. It is front-loaded and efficient.

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?

Given the tool has no parameters, the description is complete. It covers the return content and use case. The output schema exists to provide structure, so the description does not need to duplicate that information.

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 zero parameters and 100% schema coverage. The description adds value by explaining the meaning and purpose of the return values (e.g., 'total tokens analyzed' and 'warnings/errors/alerts'), which aids the agent in understanding the output beyond the 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 it returns cumulative session statistics, listing specific data points (tokens analyzed, suppressed, warning/error/alert counts). It is distinguished from sibling tools that reset stats (reset_session_stats) or configure settings (set_mode, set_thresholds), making the tool's purpose unambiguous.

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 explicitly advises using the tool to 'understand overall waste in the current session,' providing a clear use case. While it does not address when not to use it or mention alternatives, the guidance is sufficient for most scenarios, especially given the sibling tools' distinct purposes.

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