search

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds value by disclosing that results include dataset labels and that research evidence is time-bounded, which are useful behavioral traits not captured in annotations.

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 concise with two focused sentences. It front-loads the core purpose and immediately provides important context (dataset labels, time-boundedness). No unnecessary words.

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 lack of output schema and zero parameter coverage, the description is incomplete. It does not explain what constitutes a valid query, how to use the limit parameter, or what the output structure looks like beyond mentioning dataset labels. An agent needs more guidance to use this tool effectively.

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 0%, so the description bears full responsibility for explaining parameters. It mentions 'query' only implicitly and provides no details about the 'limit' parameter, query formatting, or expected input. This is insufficient for an agent to craft proper queries.

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 a specific corpus (Cities: Skylines II Wiki and research datasets) and specifies the type of information (gameplay, systems, modding). It mentions dataset labels and time-bounded evidence. However, it does not explicitly differentiate from sibling 'search_encyclopedia', leaving some ambiguity about which search to use.

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 implies usage for the bundled wiki and research datasets, and notes that research evidence is time-bounded. It does not provide explicit guidance on when to use this tool versus alternatives like 'search_encyclopedia' or other sibling tools, nor does it specify prerequisites or context.

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