discord_search

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

No annotations are provided, so the description carries the full burden. It states it performs full-text search and requires a daemon, but does not disclose if it is read-only, any rate limits, error handling, or the impact of the daemon not running. For a tool with no annotations, more behavioral context is needed.

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 a single, clear sentence that conveys the core functionality and a key prerequisite. It is concise and front-loaded, but could benefit from slightly more structure (e.g., separating prerequisite from action). No wasted words.

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 5 parameters, no output schema, and no annotations, the description is insufficiently complete. It does not mention return format, pagination behavior, sorting, what happens when the daemon is not running, or any limitations. An agent would have limited information to correctly invoke and interpret results.

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 100% parameter description coverage, so the schema already documents the parameters. The description adds no additional meaning beyond the schema, such as clarifying the search semantics (e.g., case sensitivity, match type) or parameter interactions. Baseline score is appropriate.

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's purpose: 'Full-text search across locally cached Discord messages.' It specifies the action (search), the resource (Discord messages), and a key constraint (locally cached). This distinguishes it from siblings like discord_get_messages which retrieves individual messages, and discord_send_message which sends 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?

The description mentions a prerequisite ('requires daemon') but does not explicitly state when to use this tool versus alternatives like discord_get_messages. It implies usage for full-text search, but lacks guidance on when not to use it or direct comparisons with sibling tools.

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