Describe available Catence datasets

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

The description includes 'Read-only,' which is a valuable safety signal. However, with no annotations, it does not fully disclose other behavioral traits such as output format, pagination, or whether all datasets are returned at once. It partially carries the burden but leaves gaps.

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 is a single sentence, front-loaded with the action verb 'List,' and contains no filler. It efficiently conveys the tool's purpose and key output categories.

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?

The description covers the main aspects of the tool: it lists data categories (datasets, fields, units, filters, providers, time coverage) and notes it is read-only. With no output schema, it provides enough context for an agent to understand what the tool returns, though it could be more explicit about the exact return structure.

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 tool has zero parameters, and the schema is empty. The baseline for 0 params is 4. The description adds meaning about the tool's output, but no parameter semantics are needed, so this score 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 clearly states the tool 'List cataloged datasets' with specific attributes (fields, units, permitted filters/groupings, providers, time coverage). This distinguishes it from more specific tools like 'describe_dataset', though it does not explicitly differentiate from that sibling.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that describe_dataset might be used for single-dataset details, nor any preferred context for using describe_data. The read-only hint is a behavioral trait, not usage guidance.

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