stac_collections

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

With no annotations, the description carries the burden itself. It usefully discloses that no authentication is required, which is real behavioral context, and "returns a list" implies a read-only, non-destructive call. However it says nothing about the return shape, result volume, or pagination for a collection-listing endpoint.

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?

Short and front-loaded: the core purpose and source come first, with examples and the auth note immediately after. The trailing "Args: (none)" is redundant given the empty schema and slightly dilutes an otherwise tight definition.

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?

For a zero-parameter, read-only listing tool with no output schema, the description covers what it returns, from which source, and that no auth is needed. About the only missing element is guidance on what the returned collection identifiers are for (e.g. feeding stac_search), which would strengthen routing to the sibling search tool.

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 takes zero parameters and the schema is empty, so the baseline of 4 applies. The description's "Args: (none)" simply restates what the schema already shows, adding no extra meaning, but there is nothing to document.

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?

States a specific verb and resource (returns a list of satellite data collections) scoped to a named source, AWS Earth Search, which partly separates it from the many sibling *_collections tools. It could go further by explicitly contrasting with uk_stac_collections, copernicus_collections, inpe_collections, and eodashboard_collections, but the named endpoint is enough for an agent to distinguish it.

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 examples ("AWS satellite data", "available Landsat collections") imply when an agent would reach for this tool, but there is no explicit when-to-use vs when-to-use-an-alternative guidance and no exclusions. Usage is inferable rather than stated.

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