get_recent_context

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

Annotations already declare readOnlyHint, destructiveHint, and idempotentHint. The description adds context about the in-memory buffer behavior: messages older than the buffer window are lost, and periodically calling compress_context is necessary to preserve conversations. No contradiction with 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?

The description is well-structured with a clear first sentence stating purpose, followed by return details, alternatives, and cautions. It is slightly lengthy but every sentence adds value. Could be more concise, but no redundant 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 the tool has 3 parameters, no output schema, but informative annotations, the description covers purpose, behavior (read-only, buffer loss), and alternatives. Missing details on return format specifics and error handling, but sufficient for an agent to use effectively.

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%, so the description must compensate. It implies 'target' is a group or friend but does not explain 'target_type' or 'limit' parameters. No additional details about parameter values or constraints are provided beyond the schema's defaults and titles.

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 recent messages for one group or friend from the in-memory buffer, specifying the return type. It distinguishes itself from siblings like batch_get_recent_context and compress_context by naming them and their purposes.

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 explicitly states that this is the primary tool for reading chat context, advises using batch_get_recent_context for multiple targets to reduce API calls, and recommends compress_context to archive old messages and preserve important conversations. It also warns about buffer window data loss.

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