run_eustartups_directory_search

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

With no annotations, the description carries the full burden. It usefully discloses the pricing model ('1 point per returned record'), which is real behavioral context, but omits auth requirements, rate limits, or pagination behavior for the max_items/start_page controls.

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 compact sentences, front-loaded with the core purpose and query modes. Slightly muddled by the field list 'name, city, tags, founding year, logo and link' placed after 'by keyword', which reads ambiguously as searchable fields rather than return 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 four-parameter search tool with full schema coverage and no output schema, the description covers purpose, entry modes, and cost. The main gaps are the absence of sibling differentiation and any handling note when neither country nor keyword is given.

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 the schema already documents all four parameters including the country/keyword examples. The description restates the country-vs-keyword choice but adds no syntax or format detail beyond what the schema provides, so the 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?

The description states a specific verb (Search) and resource (EU-Startups startup database) and clarifies the two query modes: by country category or by keyword. It is clearly a search tool, though it never names or contrasts against the obvious siblings run_eustartups_directory and run_eustartups_directory_categories.

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?

It gives operational guidance ('Provide a country or a keyword'), implying the two entry paths, but offers no when-to-use vs. alternatives, no statement of what happens if both or neither are supplied, and no differentiation from the directory/categories siblings.

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