summarize_session

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

Discloses that it returns only structure, not interpretation, and that coverage gaps matter. No annotations are present, so the description carries the full burden. It could mention that the tool is read-only and safe to call repeatedly, but overall it's transparent.

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?

Three concise, front-loaded sentences. Each sentence provides distinct value: output description, usage guidance, and a critical warning. No wasted 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 no output schema and no annotations, the description covers purpose, usage, and a behavioral caveat. However, it lacks parameter details and does not hint at the output format or examples. Adequate but leaves some gaps.

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 two required parameters (start, end) with no description for how to format them or what range they cover. Schema description coverage is 0%, and the description does not add any semantic meaning for the parameters. This is a significant gap.

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 a structural overview of a data session, listing specific elements (signals, samples, gaps, findings by severity). It distinguishes itself from sibling tools like run_diagnostic_rules and list_available_signals.

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?

Explicitly advises to use 'BEFORE detailed analysis' and directs to call run_diagnostic_rules for interpretation. Also warns about coverage_gaps being meaningful. Provides clear when-to-use and alternatives.

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