Ver metadata de un dataset

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety behavior is covered. The description mainly restates the shape of the returned metadata, which the output schema already provides, and adds nothing about auth, rate limits, or whether a missing id errors.

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?

A single front-loaded sentence with no filler; the colon-separated field list is compact. Slightly listy, but every element is informative and nothing is wasted.

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?

With an output schema and read-only annotations in place, the definition meets the minimum needed to call it. It still omits how to obtain a valid dataset_id and how portal selection interacts with the dataset, which is meaningful guidance for this family of tools.

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% and both the source enum and format enum are documented in the schema, so the baseline is 3. The description does not clarify that 'source' selects among multiple CKAN portals or that dataset_id accepts slugs, adding nothing beyond the schema.

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?

Names a specific verb+resource (get metadata for one CKAN dataset) and enumerates the returned fields, so the agent knows exactly what it retrieves. It does not, however, contrast itself with near siblings like get_resource_info, get_organization_info or investigate_dataset, so differentiation is left to inference.

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?

There is no statement of when to use this tool versus alternatives (e.g. search_datasets to find the id, or get_resource_info for files). The only implicit guidance is the singular 'one dataset', which is thin.

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