get_session_summary

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

Declares 'pure read' behavior and explains session boundary defined by daemon start, reset on restart. No annotations provided, but description fully covers behavioral traits.

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?

Two sections with three sentences plus two usage lines. Front-loaded with purpose, every sentence adds value. 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?

With 0 params, no annotations, and output schema present, description explains return values (aggregate counts, timestamp) and session boundary. Fully adequate for the tool's simplicity.

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?

No parameters required; input schema is empty with 100% coverage. Baseline 4 applies as description adds purpose context beyond schema, but no parameter details needed.

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?

Description explicitly states verb 'Summarize' and resource 'current ContextPulse session', listing apps, captures, voice. It distinguishes from sibling get_activity_summary by noting it's a single-call rollup for the entire session.

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?

Contains explicit 'USE WHEN' and 'NOT FOR' sections, specifying ideal use at session end and directing to get_activity_summary for arbitrary windows. Provides clear context for tool selection.

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