list_copilot_sessions

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

No annotations are provided, so the description carries the full burden. It does indicate a non-mutating list operation and adds the useful behavior of surfacing sessions waiting for permission input. However, it does not disclose any potential side effects, permission requirements, or limits on the listing.

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 concise sentences with no filler. The primary action is front-loaded, and the additional detail about permission-waiting sessions is presented in a separate short sentence.

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?

The tool is simple and has no parameters or output schema, so the description is mostly sufficient. However, it does not state what the returned list contains (e.g., session IDs, statuses) which would be needed to use sibling tools like resume_copilot_session effectively.

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 tool has zero parameters, so the baseline is 4. The description correctly focuses on the output behavior rather than parameter details, which is appropriate since there is nothing to document.

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 uses a specific verb ('List') and a specific resource ('available Copilot CLI sessions that can be resumed'), plus an additional behavioral detail about sessions waiting for permission input. This clearly distinguishes it from sibling tools that resume, run, or respond to sessions.

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 implies usage as a precursor to resuming sessions, but it never explicitly states 'use this before resume_copilot_session' or excludes the sibling tools. The context is reasonable but left to inference rather than explicit guidance.

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