get_current_session

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

The description discloses the return fields (cost, tokens, efficiency score, loops detected) but lacks details on authentication requirements, rate limits, or any side effects. With no annotations, the description carries the full burden, but it is minimally adequate.

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 sentence that is front-loaded with key information. Every word adds value, with no redundancy or filler.

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 no output schema, parameters, or annotations, the description covers the essential return values. However, it could clarify scope (e.g., per-user session) or time window, which would improve completeness.

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?

There are no parameters, and schema coverage is 100%. According to guidelines, 0 parameters warrants a baseline of 4, as there is no parameter information to provide 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 the tool retrieves details about the most recent Claude Code session, listing specific outputs (cost, tokens, efficiency score, loops detected). This differentiates it from siblings like get_session_stats which likely aggregate over multiple sessions.

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 checking the latest session details, but does not provide explicit when-to-use or when-to-avoid guidance compared to alternative tools like get_quota_status or get_usage_insights.

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