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

Discloses return behavior (snippets with IDs for fetch tool) beyond annotations. Annotations already indicate read-only and non-destructive behavior; description adds context on result format and follow-up action.

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 sentences with front-loaded purpose and key usage note. No filler, every sentence adds value.

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?

Sufficient for a broad search tool with output schema (not shown) and good annotations. Covers scope, content types, ranking mode, and next-step (fetch). Could mention limit or source defaults but schema covers those.

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?

Input schema provides full descriptions for all three parameters (100% coverage). Description adds no parameter-specific meaning beyond schema, but mentions combined ranking which relates to source. Baseline 3 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?

Description clearly states it searches all WindowsForum content (threads, posts, news) using combined keyword and semantic ranking, positioning it as the best first call. This distinguishes it from more specific sibling tools like search_posts, search_threads, and search_elastic.

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?

Explicitly states 'the best first call for any question or topic' and advises using the fetch tool for complete content. However, it does not explicitly list when to use alternatives like search_posts or search_semantic.

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