get_session_resume

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

Description aligns with annotations (read-only, safe) and adds cost context ('much cheaper'). Annotations already cover the safety profile, so description adds marginal value.

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 sentences pack purpose, usage, alternative, and return format. No fluff; every sentence earns its place.

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 optional parameter and no output schema, the description is complete: covers purpose, return format, usage guidance, and alternative. No 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?

Schema covers the only parameter 'max_sessions' fully with description and constraints. Description does not add further parameter details. Baseline 3 due to high schema coverage (100%).

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's verb 'shows' and resource 'recent past sessions', listing specific content (files, tools, dead-end searches). It distinguishes from sibling tool 'get_wake_up' by mentioning an alternative use case.

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?

Provides explicit when to use ('Call at session start'), why it's beneficial ('cheaper than re-exploring'), and an alternative ('use get_wake_up instead'). Also notes read-only nature.

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