list_ext_check_collections

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds only that results can be filtered broadly, and says nothing about pagination behavior, default page size, or what a returned check collection contains.

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?

It is short and front-loaded, but the three elements (title, endpoint path, sentence) restate each other; "List check collections" and "List and filter all check collections" are near-duplicates, and the bracketed GET path duplicates what the annotations already imply.

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?

With 12 optional parameters and no output schema, the definition is minimally sufficient for calling the tool but does not describe the shape of a check collection, its statuses, or pagination semantics, leaving an agent to infer return content entirely.

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 100% across all 12 parameters, including the orderBy format string and enum values, so the schema carries the semantic load. The description contributes no parameter meaning beyond the word "filter," which matches the baseline for fully documented schemas.

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 (list check collections) and adds the filtering capability, which is enough to separate it from the singular `get_ext_check_collection` and from `list_ext_check_collection_templates`. It never explicitly names those siblings, so differentiation is implied by the noun alone rather than stated.

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?

"List and filter all check collections" implies the browse/filter use case but gives no when-to-use versus get_ext_check_collection (single fetch) or the template-list variant, and no exclusions or preconditions. Usage is inferable but not guided.

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