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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered outside the description. The description adds only the resource-scope fact ('one PANGAEA dataset') and 'full metadata' semantics, which is useful but not extensive. No behavioral details such as error cases or response shape are given, but they are not required given the output schema.

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?

One short sentence front-loads the resource scope, ID type, and an example. Every phrase earns its place, with no boilerplate or repetition of schema fields.

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?

For a single-parameter lookup with rich annotations and an output schema, the description is fully sufficient: an agent knows what resource is accessed, how to identify it, and that the operation is non-mutating. No additional guidance is needed to 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 100% and the id parameter is described and exemplified; the description's 'numeric ID' reiterates the same constraint. It adds the concrete example 921708, but the schema already provides a matching example, so no extra semantic burden is carried. Baseline 3 is appropriate.

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 identifies a specific retrieval action ('Full metadata') on a clearly bounded resource (one PANGAEA dataset) and uniquely specifies the access path by numeric ID. It implicitly separates itself from dataset_by_doi by requiring a numeric ID rather than a DOI, and the example clarifies the identifier format.

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 its numeric ID (e.g. 921708)' tells an agent exactly when to choose this tool: when it has a PANGAEA numeric ID. It does not explicitly name dataset_by_doi or state when not to use it, but the ID-based condition and sibling list make the routing decision clear.

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