github_list_check_suites

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

With no annotations provided, the description carries the full burden but only adds routing and authentication scope details ('Routes through /api/tools/invoke under your JWT, tenant, and company scope'). It does not disclose whether the operation is read-only, destructive, paginated, or what the response format looks like.

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 short (4 lines) but at the expense of critical information. It front-loads the operation name but omits purpose, usage, and parameter details, making it under-specified rather than concise.

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 an output schema being present, the description lacks enough context for an agent to determine when to invoke this tool among many similar GitHub list operations. It does not explain the concept of check suites or how to construct the 'arguments' parameter.

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 input schema has a single 'arguments' parameter (string) with 0% schema coverage. The description states 'arguments: JSON string of arguments for the connector operation' but fails to specify what keys or values are expected, leaving the parameter essentially undocumented.

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 merely restates the operation name 'list_check_suites' without explaining what check suites are or how this tool differs from similar GitHub list tools like 'github_list_check_runs' or 'github_list_branches'. It lacks a clear verb-noun pair that defines the tool's specific function.

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?

There is no guidance on when to use this tool versus alternatives, no indication of prerequisites, and no mention of what check suites represent. The description assumes prior knowledge of the GitHub API.

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