get_all_collection_ids

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

No annotations are provided, so the description must compensate. It mentions batching but does not disclose return format, pagination behavior, or any side effects. The agent lacks key behavioral insight beyond the basic operation.

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. It is efficient but could slightly expand on parameter expectations without becoming verbose.

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 three unannotated parameters and no output schema, the description does not cover what collections are acceptable, the range of batch_size, or the impact of max_batches. The tool's behavior is underspecified for safe invocation.

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?

With 0% schema description coverage, the description adds no meaning to the parameters 'collection', 'batch_size', and 'max_batches'. It merely restates their names without explaining valid values, defaults, or usage context.

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 ('get lists of IDs') and resource ('NMDC collections') with batching detail. It distinguishes from siblings like get_collection_names and get_collection_stats which serve different purposes.

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 implies usage for 'sampling or systematic analysis of large datasets' but does not explicitly compare to other tools or provide when-not-to-use guidance. It leaves the agent to infer context without clear exclusions.

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