datasets_get

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds that the tool accepts multiple identifier formats and returns 'details', which is consistent. No additional behavioral traits (e.g., rate limits, auth needs) are disclosed, but the annotations suffice.

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, clear sentence with no extraneous information. It front-loads the action ('Get details') and resource ('one dataset'), then specifies the identifier formats efficiently.

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 no output schema, the description does not detail the return structure, but 'details' is generally understood. Given the tool's simplicity and the presence of sibling tools that might also fetch data (e.g., dataset_export), a brief note on what 'details' includes (e.g., metadata, fields) could improve completeness. However, it is adequate for a straightforward retrieval operation.

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?

With 100% schema description coverage, the parameter 'dataset' is already well-documented in the schema ('Dataset ref by id, slug, username/slug, or ul:// URI.'). The tool description repeats this format but adds no new meaning. 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 retrieves details for a single dataset, specifying multiple identifier formats (id, slug, username/slug, ul:// URI). This distinguishes it from sibling tools like datasets_list (which lists all datasets) and datasets_create (creates datasets).

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 explicitly lists the identifier formats supported, guiding usage. It implies this tool is for fetching a specific dataset, not for other operations. While it doesn't explicitly state when to avoid using it or suggest alternatives, the context of sibling tools provides clarity. A more explicit note about not using it for listing or creation would elevate this.

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