superset_get_dataset

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

In the absence of annotations, the description carries the burden of behavioral disclosure. It states that the tool returns dataset details including columns and metrics, which implies read-only behavior. It does not explicitly say 'does not modify data,' but the verb 'get' and the use case make this evident, which is adequate for a simple retrieval tool.

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 two sentences, front-loaded with the operation and followed by a relevant use case. Every word earns its place, with no redundancy or unnecessary detail.

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?

This is a simple get-by-id tool with one parameter and an output schema present. The description covers the core functionality and provides a pertinent use case, making it complete for an agent to select and invoke correctly without additional context.

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?

The schema has one integer parameter `dataset_id` with a 0% schema description coverage. The description's 'Get a dataset by id' clarifies that the parameter is the dataset's identifier, adding meaning beyond the bare schema. For a single simple parameter, this compensation is sufficient, though it could be more explicit about where to find the id.

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 explicitly states 'Get a dataset by id' with a specific verb and resource, and 'including columns and metrics' adds specific content. This distinguishes it from sibling list tools like `superset_list_datasets`, which enumerate datasets rather than retrieving a single one by identifier.

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 phrase 'Use to see available columns before creating charts' provides a clear, concrete scenario for when to use this tool. It does not explicitly mention when not to use it or name alternatives, but it gives enough context to guide the agent.

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