lobsters_search

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

No annotations provided, so the description must disclose behavior. It describes what the tool returns (title, score, comments, tags, URLs) and notes it's similar to Hacker News but more curated. It does not mention pagination behavior, rate limits, auth requirements, or how the search works beyond being a tag + keyword filter. For a simple search tool, this is adequate but minimal.

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 sentences covering purpose, context, and return data. Every phrase is informative with no redundancy. Highly efficient and front-loaded.

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 zero annotations, no output schema, and 3 parameters with 100% schema coverage, the description provides enough context about the tool's domain and return structure. It could be more complete by mentioning pagination or result limits, but for a simple search tool it is largely sufficient.

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 baseline is 3. The description adds value by explaining that the query is used as a 'tag + keyword filter', providing insight into how the search operates beyond the schema. It also lists the return fields (title, score, etc.) which enriches understanding of what to expect. This justifies a higher score.

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?

Clearly states it searches Lobste.rs for curated tech news and discussions. The verb 'Search' + resource 'Lobste.rs' is specific. The description also contrasts it with Hacker News as more tightly curated, which helps distinguish it from sibling hackernews_search.

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 explains what Lobste.rs is and that it returns title, score, comments, tags, and URLs. It implicitly suggests usage for curated tech content. However, there is no explicit when-to-use or when-not-to-use guidance relative to siblings, but the community-driven nature and curated aspect imply it's for computing-focused content.

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