context_retrieve

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

Discloses the context-aware behavior and that it returns relevant results, but does not specify that it is read-only or describe any side effects. With no annotations, this is adequate but could be improved.

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?

Three concise sentences that front-load the purpose and key differentiator. No wasted words.

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?

Covers purpose, input, and output behavior. Missing explicit mention of return format, but for a retrieval tool without output schema, this is fairly complete.

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 description maps current_focus to "what you're working on" but does not add meaning for recent_tools or limit beyond the schema descriptions. Schema covers 67% of params, so description adds marginal value.

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 it is a context-aware retrieval tool, explicitly compares to recall_insights, and describes the unique behavior of weighting by session activity, distinguishing it from siblings.

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?

Mentions similarity to recall_insights which implies when to use this over that, but does not explicitly provide exclusions or alternative scenarios.

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