ci_list_bindings

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

No annotations provided, so the description must convey behavior. It mentions that route_scopes are included when delegated, hinting at conditional output. However, it does not disclose any permissions, rate limits, or response format details beyond the listing action. For a simple read operation, this is adequate but not thorough.

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 concise with two short sentences. The first sentence states the core action and key detail (route_scopes), and the second provides usage context. No unnecessary words, front-loaded with the action.

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 no output schema, the description should clarify return values. It mentions 'inspect which GitHub Actions subjects can deploy' and 'including route_scopes when delegated' but does not describe the full response structure or possible fields. For a list tool, this provides some context but leaves ambiguity about the output format.

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 100% coverage for project_id, so the baseline is 3. The description adds no new parameter meaning; the 'including route_scopes' refers to output, not input. Since schema already describes the parameter, the description does not improve parameter semantics.

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 lists CI/OIDC deploy bindings for a project, including route_scopes when delegated. It uses a specific verb ('List') and resource ('CI/OIDC deploy bindings'), and differentiates from sibling tools like ci_get_binding (single binding retrieval) and ci_create_binding/ci_revoke_binding (mutations), as listing all bindings is distinct.

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 explicitly says 'Use this to inspect which GitHub Actions subjects can deploy before editing bindings,' indicating when to use (before editing) and providing context. However, it does not explicitly state when not to use or mention alternatives like ci_get_binding for single bindings, slightly reducing clarity.

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