resume_context

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

The description declares 'Read-only', disclosing no side effects. However, with no annotations, it does not detail behavior for default parameters or edge cases like missing sessionId. Adequate but leaves some gaps.

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: first sentence states function, second sentence gives usage guidance. Front-loaded, no redundant words, highly efficient.

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 the complexity (7 optional parameters, no output schema, no annotations), the description reasonably explains the tool's purpose, usage, and safety (read-only). Does not detail return structure but schema descriptions cover parameters.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the overall purpose of parameters (e.g., 'bias recall') and how they combine memory sources, going beyond individual schema descriptions.

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?

Clearly states the tool composes startup context by combining durable memory, patterns, cases, and latest checkpoint. The verb 'compose' is specific, and the resource is well-defined. It distinguishes from siblings by focusing on aggregation for fresh windows.

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?

Explicit use case: 'Use when entering a new session and you need to recover prior decisions, open loops, and next actions.' Provides clear context but does not mention when not to use or name alternatives.

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