Unified Context

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

Annotations already provide readOnlyHint: true. The description adds significant behavioral detail: tiered graceful degradation (full, warm, cold) and what components are combined. This goes well beyond 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 efficient sentences: first states the core purpose, second adds comparison and behavioral traits. No wasted words, front-loaded with key information.

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 5 parameters and no output schema, the description covers purpose and behavior well. Lacks explicit return value details, but the behavioral description (graceful degradation) partially compensates. Minor gap for a comprehensive context tool.

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% with descriptions for all parameters. The description adds context by explaining how certain parameters affect behavior (e.g., toolName improves lesson matching, agentType shapes context budget), enhancing understanding beyond the schema.

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 assembles a comprehensive context object in one call, listing specific components like session state, user profile, and lessons. It explicitly distinguishes from multiple sibling tools (recall, retrieve, session_primer).

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 states it replaces multiple separate calls (recall, retrieve, session_primer), giving clear when-to-use guidance. However, it does not specify when not to use it or mention alternatives for partial context needs.

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