list_copilot_seats

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

With no annotations provided, the description carries the full burden. It thoroughly discloses requirements (org owner, manage_billing:copilot or read:org scope), error behavior (404 for no subscription, 403 for insufficient access), and pagination details. It also lists return fields, making behavior highly transparent.

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 well-structured and front-loaded with the purpose. Each sentence delivers useful information: output fields, auth requirements, errors, pagination, and a docs link. No filler or redundancy; every sentence earns its place.

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?

Given there is no output schema, the description fully explains return values (assignee details, access source, dates, editor, pending cancellation). It also covers auth, error cases, and pagination, making it complete for an API tool with no annotations and no output schema.

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 only 33%, but the description compensates by explaining pagination: 'Paginate with page and per_page (default 30, max 100).' This adds meaning to page and per_page beyond the schema. It does not elaborate on org since the schema already describes it.

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 'List all GitHub Copilot seat assignments for an organization' with a specific verb and resource. It distinguishes itself from sibling tools like get_copilot_seat_details_for_user (single seat) and get_copilot_organization_details (org-level settings) by emphasizing 'all' seat assignments.

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 provides clear context on when to use the tool: to list all Copilot seats. It gives prerequisites (org owner, token scope) and error conditions (404/403). However, it does not explicitly name alternative tools or state when not to use it, so it lacks explicit exclusions.

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