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

No annotations are present, so the description carries the full behavioral burden. It names data provenance (Reddit, HN, GitHub, Stack Overflow), which is useful, but it does not disclose that this is a read-only search, how results are ranked, whether freshness matters, what source coverage is indexed, or how the limit parameter affects result behavior beyond the schema.

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 definition is a single front-loaded sentence with the action and resource first, followed by useful content/source detail. Some promotional phrasing ('battle-tested community consensus workarounds') is slightly fluffy but does not meaningfully waste space.

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 two-parameter search tool with no output schema and no annotations, the description adequately conveys the search domain and sources. It leaves gaps around return-value shape (dilemma entries, source links), ordering, and search-field coverage, so it is minimally viable rather than complete.

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 100%, so query and limit are already documented with examples and defaults. The description adds no query syntax, search-field scope, or result-ordering semantics beyond what the schema provides, making the baseline 3 correct.

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 a specific verb (Search) and resource (SaidItHere dilemmas), and enumerates content types and sources, so the agent knows this is a community-problem search tool. Sibling differentiation is only implicit via the verb contrast with get_problem and suggest_dilemma, but the core purpose is unmistakable.

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?

Usage is implied by 'Search' and the examples of query topics, suggesting this is the tool for discovery/friction lookups. However, the description never explicitly states when to use it instead of get_problem (single-item retrieval) or suggest_dilemma (submission), nor does it give exclusions or prerequisites.

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