context_assemble

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

No annotations are provided, so the description must disclose behavioral traits. It mentions assembly of replay and retrieval but does not state whether the tool has side effects, requires authentication, or what happens on error. The mention of 'greedily packed' in the max_tokens schema description is not in the tool description.

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 two sentences, front-loading the core purpose. The second sentence provides useful context about the relationship with memory_checkout. It is concise without waste, but could be slightly more informative.

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, six parameters (only one required), and no annotations, the description is insufficient. It does not explain the return value, the assembly process, parameter interactions, or how this tool differs from the sibling memory_checkout adequately.

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 only 17% (only max_tokens described). The tool description does not explain the parameters (query, session_id, replay_from_seq, limit, max_recent_events, max_tokens) beyond the vague mention of 'replay' and 'ranked retrieval.' It fails to compensate for low schema coverage.

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 action: 'Assemble replay plus ranked retrieval into a prompt-ready context bundle.' It distinguishes from siblings by mentioning 'memory_checkout, the front door, wraps this assembly,' implying this is a lower-level tool. However, it could be more explicit about the primary function.

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 that context_assemble is used internally or directly when the full wrapping of memory_checkout is not needed. No explicit guidance on when to use vs. alternatives, nor any exclusions or prerequisites.

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