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

The description discloses the key behavior of returning null when the dataset is absent, which goes beyond the readOnlyHint annotation. It does not mention rate limits or auth, but the read-only nature is covered by annotation.

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, concise sentence that packs essential information without superfluous details. It is well-structured and easy to parse.

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 provides the core purpose and null behavior, but lacks details on optional parameters and the shape of 'full metadata'. Since there is no output schema, more context on the return type would be helpful.

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?

Only dataset_id is hinted at in the description ('the id search_datasets returned'). The optional parameters as_of and snapshot_id are completely unexplained, and the description does not compensate for the 0% schema coverage.

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 full metadata for a single dataset by ID, and explicitly notes the null return when absent. This distinguishes it from sibling tools like search_datasets and list_organizations.

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 'by the id search_datasets returned' implies the tool is used after search_datasets to fetch details for a specific dataset. While not explicitly contrasting with alternatives, the context of sibling tools makes the use case evident.

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