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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds behavioral context: it notes the underlying API is a CKAN-compatible shim and explicitly states 'no auth required.' It does not discuss rate limits or error handling, but for a read-only detail endpoint the added context is sufficient given the annotation coverage.

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 a single, information-dense sentence that front-loads the core purpose before listing returned fields. It also includes the API source and auth note. While it is not extremely terse, every clause adds useful information. The structure is clear and scannable, though the list of fields could be seen as slightly verbose.

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?

The description explains what the tool returns (localized title/description, source catalogue, tags, license, distribution list) and the data source. With an output schema present and full schema coverage for parameters, the description covers the essential context for an agent to call the tool correctly. It does not mention error cases or pagination, but these are not critical for a simple detail lookup.

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% – both parameters (id and locale) have descriptive comments in the input schema, including an example for id. The description does not add significant semantic value beyond the schema; it mentions localized fields which map to the locale parameter, but this is already implied by the schema. With full schema coverage, a baseline of 3 is appropriate.

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's purpose: 'Get full metadata for one EU Open Data Portal dataset by id' and enumerates the specific metadata fields returned. This distinguishes it from sibling tools like data-europa.datasets.search, which is for finding datasets, and the reference tools for catalogues and themes. The verb 'Get' and resource 'dataset detail' are specific.

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: you call this when you have a specific dataset id and need full metadata. The id parameter description explicitly says the id comes from dataset_search results, providing context on how to obtain it. However, it does not explicitly state when NOT to use this tool or name alternatives directly, though the sibling set makes it obvious that search is for discovery. The mention of 'no auth required' is useful guidance for the agent.

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