cbs_list_datasets

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds limited behavioral context. It does disclose the return format (CSV string with columns), which is helpful. No additional behaviors (e.g., pagination details beyond what schema provides) are described.

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 concise with no unnecessary words. It uses a clear structured format (Args, Returns) that is easy to parse. Every sentence adds value.

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 tool's purpose, parameters, and return format adequately. An output schema exists (not shown), but the description states the CSV columns, which is sufficient for understanding what the tool does. Could mention error handling or rate limits, but not essential for a read-only list operation.

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?

Input schema coverage is 100%, and the description repeats parameter defaults and boundaries already present in the schema. It adds explicit default values (10 for top, 0 for skip), but this is marginal value. The baseline of 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 clearly states 'Lists available datasets from the CBS OData Catalog', which is a specific verb+resource. However, it does not explicitly differentiate from siblings like 'cbs_search_datasets' or 'cbs_list_local_datasets', which could cause confusion about when to use this 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?

No guidance is provided on when to use this tool versus alternatives. Siblings exist (e.g., search, local), but the description does not mention them or specify scenarios. This leaves the agent to infer usage without support.

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