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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it's safe. The description adds a crucial constraint: only GERDA datasets are listed (not all datasets on the server), which is valuable context beyond the annotations.

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?

Single sentence, under 10 words, with the key qualifier ('GERDA') front-loaded. Zero waste.

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 no-parameter, list operation with a given output schema, the description is mostly complete. It might be improved by hinting at the output structure (e.g., a list of dataset names), but the presence of an output schema reduces that need. What else is missing is minimal.

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?

No parameters, so the schema provides no parameter info. The description compensates by clarifying that it's a server-wide listing of GERDA datasets, which is the only semantics needed. Baseline for 0 params is 4, and the description leverages that well.

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?

States a specific verb ('List') and resource ('GERDA datasets'), and mentions the server scope. It is distinguishable from siblings like describe_dataset and query_results, but could explicitly differentiate itself from find_geographies which might overlap in listing data.

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?

Clearly implies listing all available datasets, which is appropriate for initial exploration. However, it does not explicitly state when to use this over describe_dataset or query_results, nor does it mention alternative tools for more specific searches.

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