get_queryables

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

No annotations are provided, so the description carries full burden. It only states the operation is a retrieval ('Get'), but fails to disclose any behavioral traits such as side effects, authentication requirements, rate limits, or data volume. The read-only nature is implied but not explicit.

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 a single, efficient sentence. Every word contributes to understanding the tool's core function with no extraneous 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?

Despite having an output schema (which mitigates need for return value explanation), the description is minimal. It fails to provide context for the optional parameter, usage scenarios, or integration with siblings. The tool's behavior relative to the STAC specification is not explained.

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 coverage is 0%, so description must compensate. It mentions 'by its ID' for collection_id but does not clarify that the schema expects an array of strings, which could mislead agents expecting a single string. The optional catalog_url parameter is entirely undocumented in the description.

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 tool's purpose: retrieving queryable properties for a specific STAC collection by ID. It uses a specific verb ('Get') and resource ('queryable properties for a specific STAC collection'), distinguishing it from siblings like 'get_collection' which retrieves the collection itself.

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 context (need a collection ID) but does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria. No sibling comparisons or when-not scenarios are mentioned.

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