Upload a dataset to Realia

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

Annotations establish that this is a mutating, non-idempotent operation. The description adds meaningful behavioral context beyond that: the dataset becomes publicly searchable, the schema and sample row are inferred, content must be passed directly, and there is an 8 MB limit. No contradiction with annotations exists.

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?

Four compact sentences deliver the purpose, invocation detail, behavioral side effects, and constraint with no filler. The most important information is front-loaded, and every sentence earns its place.

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 five parameters, annotations, and the presence of an output schema, the description covers the essential operational context: token ownership, raw content encoding, public visibility, schema inference, and the size limit. Return values are already handled by the output schema, so nothing critical 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?

Schema coverage is 100%, so the baseline is 3. The description adds genuine value by clarifying that `content` must be raw file text rather than a path, by narrowing supported formats, and by noting the size constraint. This supplements the schema without merely repeating 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 states a specific verb ('Publish'), a concrete resource ('dataset to Realia'), and the supported formats (CSV, TSV, JSON). It also scopes the operation to the token's account, making it unambiguous versus the read-oriented sibling tools like search_datasets, get_dataset, and list_launchpad.

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 clearly implies when to use this tool: when an agent needs to make dataset contents publicly available under the current token. It does not explicitly name exclusions or alternatives, but the sibling tools are functionally distinct enough that the intended usage is clear.

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