list_collections

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

With no annotations provided, the description carries the burden. It discloses the return fields (collection names, table names, field counts) and implies a read-only listing operation by using 'List'. It also notes that this is not the full-schema view, pointing to get_collection. However, it does not disclose pagination behavior, which may conflict with 'List all' when page/limit parameters exist.

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 primary purpose. The first sentence states the action and resource, and the second sentence adds output details and an alternative. There is no filler or redundancy.

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 purpose, output fields, and an alternative for deeper detail, which is sufficient for a simple list tool. However, it omits pagination specifics and does not clarify that the 'all' might be limited by page/limit parameters. Given the absence of annotations and output schema, this is nearly complete.

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?

All three parameters (page, term, limit) have descriptions in the schema, so the description adds minimal semantic value beyond the schema. It does not explain how to use these parameters together or what 'all' means in the context of pagination.

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 action ('List all database collections') and the resource ('for the site'), and distinguishes itself from the sibling tool get_collection by noting that get_collection provides full schema details. This is a specific verb+resource combination with a clear scope.

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 explicitly points to get_collection as the alternative for full schema details, which tells the agent when not to use this tool. However, it does not mention other related tools like query_collection_records or clarify conditions such as pagination usage, so it is clear but not exhaustive.

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