list_resources

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds that the tool returns 'formats and sizes' of resources, which provides behavioral context about the output beyond the annotations. No contradictions.

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 consists of two concise sentences: one stating the purpose and output, and one specifying the parameter. It is front-loaded with the main action and contains no unnecessary information.

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?

Given the tool has one parameter and an output schema, the description is complete. It explains the tool's purpose, the parameter's format, and what the output contains (formats and sizes). The output schema likely details the return structure, so no additional explanation is needed.

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 input schema has one parameter 'dataset_id' with 0% description coverage (no schema description). The description compensates by providing a clear explanation and example ('e.g. "toronto:ttc-ridership" or bare ID'), adding significant semantic value beyond the schema.

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 lists all resources (files) in a dataset with their formats and sizes, using the verb 'list' and specifying the resource and output details. It distinguishes itself from siblings like 'download_resource' and 'get_resource_schema' by focusing on listing resources within a dataset.

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 does not explicitly state when to use this tool versus alternatives like 'get_dataset_info' or 'download_resource'. The usage is implied (list resources in a dataset), but no guidance on when not to use it or which sibling might be more appropriate is provided.

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