discord_search

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'search messages' but does not reveal whether it is read-only, whether it searches across all channels, what the response format is, or any rate limits or permissions required beyond a bot token.

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 very short (4 words), but it is underspecified rather than concise. It lacks structure and fails to provide necessary details. It does not front-load critical information beyond the basic verb+resource.

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 no output schema, no annotations, and 5 undocumented parameters, the description is severely incomplete. It does not explain what the search returns, how to construct queries, or any prerequisites like the bot token's role. The agent would struggle to use this tool correctly.

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?

The input schema has 0% description coverage, meaning none of the 5 parameters have descriptions. The tool description adds no semantic information about parameters like 'content', 'author_id', or 'channel_id', leaving the agent to guess their function.

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 states the verb 'search' and resource 'messages' in a 'Discord guild', providing a basic purpose. It distinguishes from sibling tools like discord_read or discord_channels by indicating search rather than read or list, but lacks specificity on scope (e.g., across channels) and fields.

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?

No guidance is provided on when to use this tool vs alternatives like discord_read or discord_search. There is no mention of contexts where this tool is appropriate or not, and no references to other tools for comparison.

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