prepare_synthesis_context

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

The description indicates that the tool is read-only and returns existing context, but does not disclose details about the context structure, potential side effects, or authentication requirements. With no annotations, the description carries the burden and is adequate but not thorough.

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 a single clear sentence with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose.

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?

While the tool is simple (no parameters), the lack of an output schema means the description should explain what the returned context contains. It only says 'same context exposed by the synthesize_memories prompt,' which is vague and relies on the agent's prior knowledge.

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 input schema has no parameters, so schema coverage is 100%. The description does not need to add parameter information. Per the guidelines, 0 parameters gives a baseline of 4.

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 that the tool returns the context from the synthesize_memories prompt, packaged as a tool result. This is specific and distinguishes it from siblings by name, but does not explicitly differentiate from similar context-retrieval tools like prepare_memory_city_context.

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 mentions that this tool is for 'prompt-limited clients,' which gives some context for use, but provides no guidance on when to use this tool over its siblings such as prepare_memory_city_context or prepare_packetized_synthesis_context.

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