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

No annotations exist, so the description carries the full burden. It discloses that calls use the caller's OpenAny gateway credentials and that charges/authorization are gateway-determined, which is genuinely useful cost and auth context, but it omits rate limits, result counts, failure modes, and pagination behavior beyond what the schema states.

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?

Three tight sentences, front-loaded with the search verb and return shape, followed by the Fetch fallback and then the billing caveat. No filler or redundant restatement of schema fields.

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 15-parameter tool with no annotations and no output schema, the description supplies the essentials: what comes back (ranked results, snippets, source URLs), when to escalate to Fetch, and how billing/authorization work. Minor gaps remain around result volume and pagination caps, but the high schema coverage carries the parameter burden.

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 every parameter is already documented in the schema, including domain_type, date filters, and pub_year bounds. The description only hints at the three domain types and adds no syntax or interaction detail (e.g., that pub_year_* apply only to research_paper), so baseline 3 applies.

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?

'Search the web, news, or research papers and return ranked results with snippets and source URLs' gives a concrete verb, resource, and return shape, resolving the opaque tool name tinyfish_get. It clearly separates itself from the page-fetch sibling, but says nothing to distinguish it from the many other search tools in the sibling list.

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 routes the agent: use Fetch when full page content is required, implying this tool is for discovery/snippets. That is a clear alternative with a stated condition, though there is no guidance on when this search backend beats the other search siblings or on query construction.

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