get_recent_context

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

Discloses that messages are buffered (backfill+real-time) and returned as URLs in image_urls field. Lacks details on rate limits, authentication, or error behavior, but overall decent for a read-only tool.

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?

Concise and well-structured with a clear Args section. Every sentence adds value without redundancy.

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 main behavior (uncompressed, buffered, image URLs) but missing details on error handling, validation, or what happens when target is not monitored. Adequate but not thorough.

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?

With 0% schema coverage, description fully explains each parameter: target (Group ID or friend QQ), target_type (group/private), limit (default 200). Adds clarity beyond raw 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?

Clearly states it retrieves recent message context for monitored groups or whitelisted friends. Differentiates from sibling 'compress_context' by noting it returns uncompressed messages.

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 recommends 'compress_context' as an alternative for compression. However, does not clarify when not to use this tool or prerequisites like needing to have the target monitored.

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