Read Dataset Evidence Passport

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

Beyond the annotations, the description candidly discloses what the Passport is not: semantic truth, completeness, certification, legal permission, safety, or AI admission. It also clarifies the operation is read-only and artifact-bounded, adding meaningful behavioral context beyond the readOnly and idempotent hints.

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?

Three sentences, each with a distinct role: one states the output, one restricts the operation's scope, and one clarifies the semantic boundaries. No filler or redundancy; the key constraints are front-loaded.

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 a single parameter, rich annotations, and an output schema present, the description is complete. It addresses selection criteria, operational boundaries, and semantic interpretation, leaving no critical gap for an agent deciding to call the tool.

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 already documents the only parameter, including an example and a description, so the baseline is 3. The description simply refers to a 'canonical dataset ID' without adding extra syntax or format detail, and the schema covers 100% of the parameter semantics.

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 uses a specific verb ('Return') with a precise resource ('one bounded, machine-readable Dataset Passport v1') and target ('canonical dataset ID'). It clearly distinguishes this tool from siblings by stating it reads only the published Passport artifact rather than fetching upstream sources or creating evidence.

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: this tool is for obtaining the published Passport v1 artifact and should not be used to fetch upstream sources or generate evidence. It does not explicitly name alternative sibling tools, but the scope and exclusions are explicit enough to guide an agent.

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