unified_context

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

The description discloses tiered graceful degradation (full → warm → cold) and orchestration behavior beyond the readOnlyHint annotation. No contradiction with annotations.

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, no fluff. The first sentence states the primary purpose, the second adds key differentiators and behavioral detail. Front-loaded efficiently.

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?

The description covers the high-level purpose and behavioral traits (degradation). For a tool with 5 parameters and no output schema, it could be more explicit about return structure, but it is reasonably complete for orchestration context.

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 each parameter already has clear descriptions. The description adds minimal extra meaning beyond summarizing the purpose of the parameters collectively.

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 verb 'Assemble' and the resource 'complete, role-aware context object', and explicitly distinguishes it from siblings (recall, retrieve, session_primer) by claiming it replaces multiple calls.

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 when to use: when needing a comprehensive context in one call instead of multiple separate calls. It does not explicitly state when not to use or provide alternative conditions, but the replacement hint gives clear context.

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