find_in_recent_history

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

Discloses that scanning is local, which is valuable given no annotations. However, misses detail on limitations, permissions, or memory impact; half the burden is carried by 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?

Two concise, front-loaded sentences. Each sentence earns its place.

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?

Missing key context for a complex 11-parameter tool: how 'recent' is defined, result format, pagination beyond before_message_id, and local scanning scope. Inadequate without output schema or annotations.

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 only 9%, and the tool description adds no parameter details. Agents must infer meaning from names alone, which is insufficient for 11 parameters.

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 scans recent channel history locally, differentiating it from siblings like search_guild_messages by specifying 'local' and mentioning use when native search indexing is delayed.

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?

Provides clear context: useful when native Discord search indexing is delayed or a bounded recent search is needed. Does not explicitly exclude alternative tools but implies it is for quick local scans.

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