run_betalist_startups_search

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

With no annotations, the description carries the full burden, and it discloses two useful traits: the returned fields (name, tagline, logo, link) and the cost model ('1 point per returned record'). That is real added context, but it says nothing about pagination behaviour for start_page, empty results, or rate limits.

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 short, front-loaded sentences with no filler. The cost sentence earns its place by warning about per-record charges, though the returned-field list could have been deferred to an output schema.

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?

With no output schema and no annotations, the description does cover the return fields and cost, which are the two things structured data cannot supply here. However, it omits pagination semantics despite a start_page parameter and gives no sibling routing, leaving gaps for a search tool in a crowded family.

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%, with keyword, max_items (up to 250) and start_page all documented in the schema, so the baseline is 3. The description lists output fields rather than parameter meaning and adds nothing beyond what the schema already provides.

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?

States a specific verb and resource ('Search BetaList startups by keyword') and lists the returned fields, so the agent knows exactly what the tool does. It fails to distinguish itself from the close siblings run_betalist_startups, run_betalist_startups_latest and run_betalist_topics_startups, which is the only thing keeping it from a 5.

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?

There is no when-to-use guidance and no mention of the alternatives, despite several BetaList siblings that overlap heavily. The keyword-search nature is implied by the name, but the agent gets no rule for choosing this over run_betalist_startups_latest or run_betalist_topics_startups.

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