session_tools

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It fails to mention that the tool is read-only or any safety traits, leaving the agent uncertain about side effects or permissions. A simple statement of read-only nature would improve this.

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, front-loaded with the primary purpose and a concise use case. Every word adds value without redundancy.

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?

For a simple tool with one parameter and no output schema, the description fairly covers the output details and purpose. However, it lacks explicit read-only confirmation and does not mention the return format, which would make it more complete.

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 schema has one parameter (session_id) with no description (0% coverage). The tool description does not explain the parameter further, such as format, example, or how to obtain it. It only mentions 'given session', which is insufficient for an agent to correctly determine the value.

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 shows detailed usage data for a specific session, including call counts, response sizes, and latency. It uses specific verb 'Show' and identifies the resource and metrics, distinguishing it from siblings like recent_sessions and usage_summary.

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 provides a clear use case: 'Helps debug why was this session expensive/slow'. It implies when to use it but does not explicitly state when not to use it or mention alternatives, though sibling tool names provide some context.

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