singapore_list_collections

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

Annotations already establish that this is a safe, read-only, idempotent, non-destructive open-world operation. The description adds useful behavioral context by noting that the page is live and that page size is controlled by the provider, which matters for pagination expectations.

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 two sentences, front-loaded with the main action and resource, and contains no filler. Every sentence contributes useful 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?

The tool is simple, has an output schema, and has rich safety annotations, so the description need not explain return values or permissions. However, it omits selection guidance relative to sibling collection tools and does not document the page parameter, leaving some gaps for an agent choosing and invoking it.

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 0% for the sole page parameter, so the description must compensate. It mentions a 'page' and provider-controlled page size, but does not explain that the parameter selects the page number or clarify its range/default behavior.

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 gives a specific verb and resource: list data.gov.sg collections and their child dataset IDs. It is clear what the tool returns, but it does not explicitly distinguish itself from sibling tools such as singapore_get_collection or singapore_search_catalog.

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?

It states what the tool lists but gives no explicit guidance on when to use it versus alternatives like singapore_get_collection or singapore_search_catalog. There are no exclusions or selection conditions beyond the implicit collection-listing purpose.

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