get_recent_context

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

No annotations provided, so description carries full burden. It discloses the tool is read-only ('only reads when you ask'), but does not describe return format, side effects, or other behaviors. Output schema exists but is not referenced in description.

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 bilingual with Chinese and English, adding length. Each sentence adds value, but the duplication is unnecessary. Key info is front-loaded with English 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?

For a simple read tool with 2 optional params, the description covers purpose, usage context, and parameter semantics. It lacks explicit return info, but output schema exists. Overall adequate.

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 description coverage is 0%, but description adds meaning: explains 'tool' as optional and behavior when empty, explains 'limit' with default. This compensates for missing schema descriptions, though not exhaustive.

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 retrieves the most recent AI conversation context, using specific verbs ('Retrieve') and resource ('recent AI conversation context'). It distinguishes from sibling tools like get_project_context by focusing on recovery after context loss.

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?

Explicitly states when to use: 'after context loss (tool restart, session disconnect)'. It also clarifies it does not auto-load, implying it's a read-only manual action. However, it does not explicitly mention when not to use or compare to alternatives.

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