reach_search

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

Description alerts to prerequisites (OpenCLI for some platforms) and gives platform-specific behavior, but lacks broader behavioral details like error handling or data handling. No annotations exist, so the description carries the full burden but does not fully address it.

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?

Single sentence with a list; efficient and front-loaded with the core action, though the list is somewhat dense.

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?

Covers many platforms and key prerequisites, but omits output description and error scenarios, leaving gaps for a search tool.

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?

With 0% schema coverage, the description compensates well by detailing the platform parameter's options and context, and implies query usage. However, the limit parameter is not described.

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 searches various platforms and lists them explicitly, making its purpose distinct from sibling tools like reach_hot or reach_research.

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 on when to use this tool over siblings; no when-not or alternative recommendations.

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