Search Realia datasets

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is established. The description adds behavior beyond annotations: search across title/description/column name, empty query for newest entries, and the lightweight return shape (id, size, field names).

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 short sentences earn their place: the first scopes the operation, the second states the return envelope, and the third covers empty-query behavior and routes to get_dataset. No filler or repetition 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 read-only search tool with full schema descriptions and an output schema, the description covers what the tool returns, how to get more detail, and a special case (empty query). Nothing required for a correct call is missing.

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?

The input schema already describes query and limit at 100% coverage, so the baseline is 3. The description adds meaning by clarifying that query matches title, description, or column name and that leaving it empty returns the newest datasets, which is not expressed in the schema descriptions.

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 names a specific verb ('Search'), a clear resource ('real-world datasets published on Realia'), and the fields searched (title, description, column name). It also distinguishes itself from get_dataset by stating what it returns, so an agent can tell it apart from siblings.

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 implicitly establishes when to use the tool: for lightweight discovery/searching by text, and explicitly routes follow-up needs to get_dataset for 'full schema and a sample row'. It does not discuss sibling tools like upload_dataset or list_launchpad, but those are not relevant to this search operation.

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