render_active_sessions

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

Annotations indicate no strong side effects (readOnlyHint false, destructiveHint false, idempotentHint true). The description adds valuable behavioral context: data source (local transcripts + Oracle API), defaults (24h, top 10), and an explicit instruction to print the `text` field verbatim. This goes beyond annotations without contradicting them.

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 concise and front-loaded with the core purpose, then provides source, output handling, and defaults. Every sentence carries distinct information, with no fluff or repetition.

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 tool with 3 optional parameters and no output schema, the description adequately covers purpose, data source, output handling, and defaults. Minor gaps exist: it does not explain what 'effective/nominal cost' means or whether any prerequisites are needed, but these are not critical for basic usage.

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?

Schema description coverage is 100% for all three parameters. The description additionally clarifies that `hours` defaults to 24 and `limit` defaults to 10, and that `cwd` limits to a working directory, enriching the schema's explicit definitions.

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 specifies the tool renders a pre-formatted table of recent Claude Code sessions with detailed metrics (Prompts, Inferences, Tool calls, tokens, costs). However, it does not explicitly differentiate from the sibling tool 'render_session_report', which could serve a similar purpose, so it lacks full sibling distinction.

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 display (print text verbatim) and notes default look-back and limit, but it does not explicitly state when to use this tool over alternatives like 'render_session_report' or whether it complements 'analyze_session'. No exclusions or alternative recommendations are provided.

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