context_recovery

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

Discloses it returns recent summaries and accumulated state. Lacks details on auth needs, rate limits, or any side effects. No annotations provided, so description carries burden but is not comprehensive.

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 sentences, front-loaded with purpose. The line about 'prosthetic's core value' is somewhat poetic but adds minimal clarity; overall concise and to the point.

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?

Despite having an output schema, the description omits parameter semantics and any indication of output structure beyond 'recent summaries + accumulated state'. Incomplete for effective agent use.

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?

Input schema has 2 parameters (domain, summary_count) with 0% description coverage. Description does not explain what domain represents or how summary_count affects results, leaving the agent with no guidance.

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?

Clearly states it returns a 'waking up' brief for re-entering a domain, including recent summaries and accumulated state. Distinguishes from siblings like get_conversation or search_summaries by focusing on full context recovery.

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?

Implies usage when re-entering a domain, stating 'making re-entry cheap'. No explicit when-not-to-use or alternative tools mentioned among the many siblings.

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