show_dataset

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

With no annotations provided, the description carries full burden for behavioral transparency. 'Get details' implies a read-only operation, but it does not explicitly state that no modifications occur, nor does it disclose permissions, rate limits, or data retention policies. The description is minimally adequate.

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, front-loaded sentence of 12 words with no filler. Every word is meaningful, making it highly scannable and efficient.

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 tool's simplicity (1 parameter, no output schema, no annotations), the description is sufficient for basic understanding. However, it lacks context on response format (e.g., shape of metadata) and any caveats about data freshness or accessibility, leaving room for confusion.

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% for the single parameter (dataset_id as UUID string). The description adds no additional context or constraints beyond what the schema already provides, so it does not improve parameter understanding.

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?

Description starts with 'Get details of a specific dataset', clearly stating the verb 'Get' and resource 'dataset'. It lists specific included fields (status, source, metadata) which distinguishes it from sibling tools like list_datasets (list all) or create_dataset (create new).

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 for retrieving details of a single dataset, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., list_datasets for overview, show_evaluation for evaluation details). No exclusions or prerequisites are mentioned.

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