session_stats

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

With no annotations, the description carries full burden. It explains what statistics are shown and mentions the RAG savings comparison. However, it does not explicitly state that the tool is read-only or non-destructive, which would be helpful for behavioral transparency.

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 extremely concise with two sentences and a usage note. It is front-loaded with the purpose and contains no redundant or 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?

Given 0 parameters and the presence of an output schema (as indicated by context), the description covers the what and when of the tool adequately. It could mention if it has side effects or if it can be called multiple times, but it is sufficient for a simple 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 input schema has 0 parameters, so baseline is 4. The description adds meaning by enumerating the specific statistics displayed (token usage, RAG savings, patterns learned), which the schema cannot convey.

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 'Show' and identifies the resource as 'session efficiency statistics' with details on what it includes (token usage, RAG savings, patterns learned). This clearly distinguishes it from sibling tools like 'reset_session_stats' which resets instead of showing.

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 states when to call it: 'at the end of multi-step tasks or when asked about efficiency.' This provides clear context for usage. It could also mention when not to use it, but the positive guidance is sufficient.

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