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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond those hints: the data source URL, the NOAA NCEI agency, the fact that no authentication is required, and the types of data returned. This meaningfully enriches what an agent knows before invoking the 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?

Two sentences contain no filler: the first states what the tool returns and the identifying key, and the second provides source and authentication context. Every sentence earns its place and the most important behavioral information is 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?

For a single-parameter, read-only, idempotent lookup tool with a complete input schema and an output schema available, the description is sufficient. It covers the source, authentication requirement, return contents, and identifier semantics. Nothing an agent needs to decide whether to call it and how to call it is missing.

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%, so the schema already fully documents the single parameter, including an example value and where to obtain it. The description adds the context that this parameter identifies a single study, but no additional format, constraints, or derivation details beyond what the schema provides. 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 uses a specific verb ('Get full detail'), names the exact resource ('single NOAA NCEI Paleoclimatology study'), and identifies the key identifier ('NOAA Study ID'). It also enumerates the return contents (investigators, publications, site coordinates, per-site data tables, download links), making the tool's purpose unambiguous and distinguishable from the sibling search tool.

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 implies the correct usage context: this detail tool is for when a NOAA Study ID is already known, and the parameter schema explicitly says the ID is 'obtained from paleoclimate.study_search results.' It does not explicitly name sibling tool paleoclimate.study.search as the alternative, but the 'by NOAA Study ID' qualifier and source of the ID make the usage context clear.

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