ads_discord_message_search

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

With no annotations, the description carries the burden and does disclose key behavior: it searches only a bounded recent page and does not crawl or persist history. It omits auth/rate-limit details and pagination mechanics, but the non-persistence constraint is meaningful.

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?

A single front-loaded sentence with no filler. The semicolon clause adds a real behavioral constraint rather than restating the name.

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 five-parameter search with no annotations, no output schema, and 0% schema descriptions, the definition is too thin. It explains scope but not parameter semantics or return shape, so an agent lacks enough detail to invoke it confidently beyond channel_id.

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 coverage is 0% and the description names no parameters. 'One accessible Discord channel' and 'bounded recent page' loosely hint at channel_id and before/after/limit, but query, limit bounds, timestamp formats, and required channel_id are undocumented.

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 gives a precise verb (Search), resource (messages), and scope (one accessible Discord channel, bounded recent page). It also rules out crawling/persistence, helping distinguish it from channel list, member search, and send siblings.

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?

It establishes clear usage context: single channel, recent bounded page, no history crawl. It does not explicitly name alternatives or when-not-to-use cases, but the scope is sufficient to prevent broad-history use.

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