accelerator_search

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

No annotations are provided, and the description does not disclose behavioral traits such as read-only status, pagination, rate limits, or authentication requirements. The agent is left to assume safe, query-only behavior without explicit confirmation.

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?

The description is very concise (10 words) and front-loaded with the main action and resource. However, it omits additional context that could be included without harming conciseness, such as default behavior or output hints.

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 the presence of an output schema and well-described parameters, the description is minimally adequate. It lacks clarity on whether all parameters can be omitted to return all results, and does not mention any limits or pagination. For a tool with zero required parameters, this omission is a gap.

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 coverage is 100%, so the detailed parameter descriptions already explain each field. The description re-states filtering by 'sector, cost, and location' but adds no new semantic nuance beyond summarizing the schema. This meets the baseline but does not exceed it.

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 that the tool searches UAE accelerators and incubators by sector, cost, and location. It uses a specific verb ('Search') and identifies the resource ('UAE accelerators and incubators'). While it is distinct from most siblings due to its specific domain, it does not explicitly differentiate from other search tools.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, exclusions, or typical use cases. An agent would have to infer usage context from the tool name and parameters alone.

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