list_ext_check_collection_templates

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds only the bare hint that filtering is supported; it says nothing about pagination behavior, default page size, sort defaults, or what a result set contains, so it barely exceeds what the structured fields provide.

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?

Two short lines with the resource front-loaded and no filler prose. Slight redundancy: the title, the first phrase, and the second sentence all restate the same resource name.

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?

Annotations and a fully documented schema make the tool callable, and no output schema exists so return-value detail isn't mandatory. Still, a list-and-filter tool with 9 optional parameters would benefit from stating that results are a paginated collection of templates and how filtering by objectType/time ranges scopes them.

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 9 parameters, including page/size/orderBy and the creation/modification time ranges, so the schema carries the semantics. The description adds no parameter-level meaning beyond the word "filter".

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 collection templates) and repeats it in slightly expanded form with filtering. An agent can distinguish it from list_ext_check_collections and get_ext_check_collection_template by the name/description alone, though the description never makes that distinction explicit.

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 collection templates" implies the tool is for browsing filtered template catalogs, but there is no statement of when to use it instead of get_ext_check_collection_template or list_ext_check_collections, and no prerequisites or exclusions.

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