list_dataset_parents

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

With no annotations provided, the description carries the burden of disclosure. It explicitly explains recursive behavior, version semantics, and the return format. It does not mention permissions or error cases, but as a non-mutating listing operation, these omissions are not critical. The description is reasonably transparent for the tool's simplicity.

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 well-organized: a succinct summary, then Args, Returns, and Example sections. Every sentence contributes meaningful information without repetition, and the structure makes it easy to scan.

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 simple read-only nature of the tool and the presence of an output schema, the description covers all necessary usage aspects: parameters, return shape, and examples. It explains recursion and version handling adequately, leaving no significant gaps for an agent to select and invoke the tool correctly.

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 0%, but the description fully compensates by defining each parameter, including dataset_rid, recurse with a default and behavior, and version with an example and fallback rule. The example further clarifies parameter usage, making semantics clear 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?

The description opens with a specific verb+resource: 'List all parent datasets that contain this dataset as a child.' This clearly identifies the operation and its scope, distinguishing it from sibling tools like add_dataset_child. The one-sentence summary leaves no ambiguity about what the tool does.

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 provides clear context through parameter explanations and examples, showing when to use recurse=True vs. False and the optional version. However, it does not explicitly name alternatives or state when not to use this tool, so it lacks exclusions but still offers clear usage context.

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