list_ext_checks

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 covered. The description adds only the HTTP method/path; it says nothing about pagination behavior, default page size, or whether unfiltered calls return everything.

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?

Very short, but wasteful: 'List check' and 'List and filter all check' restate each other, and the phrase is ungrammatical. The endpoint breadcrumb is useful and front-loaded, but the payload beyond it is near-zero.

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 13-parameter list tool with no output schema, the description gives no sense of what a 'check' is, what result fields come back, or how paging/ordering interact. The complete schema descriptions carry almost the entire burden here.

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%, so all 13 parameters (including enums for status and objectType, and the orderBy format) are already documented in the schema. The description adds no parameter meaning beyond the word 'filter', so baseline 3 applies.

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 states a verb+resource (list checks, with filtering) and includes the endpoint GET /v1/troubleshooting/checks, which confirms a read operation. However, 'check' is never defined, and nothing distinguishes this from sibling get_ext_check or list_ext_check_collections beyond the plural 'all'.

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?

No when-to-use or when-not-to-use guidance. The agent is left to infer that this is the bulk enumeration tool versus get_ext_check (single check) and list_ext_check_collections (collections) purely from the names.

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