List Workspace changesets

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this with "No run starts and nothing changes" — the key safety fact for a workspace agent. It also discloses pagination behavior, which the annotations do not cover. It does not describe ordering or cursor invalidation, keeping it below the top mark.

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?

Three short sentences with zero waste: scope first, then the sibling-routing hint, then the safety guarantee. Every sentence earns its place and the most important constraint is front-loaded.

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 an output schema present and full schema coverage, the description need not explain return values, and it covers pagination and side-effect freedom. Minor gaps remain: result ordering and what happens on an expired cursor are unstated.

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 coverage is 100%, so the schema already documents limit, cursor and workspace_id, putting the baseline at 3. The description adds meaning by framing the call as "one page at a time," which explains why cursor and limit exist together as a pagination pair rather than independent filters.

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?

States a specific verb and resource ("List the changesets of a Workspace") plus the exact fields returned (state, phase, changed path count). It explicitly distinguishes itself from get_workspace_changeset, so an agent can pick between them without opening either schema.

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?

"get_workspace_changeset returns the changed paths" is an explicit routing rule to the sibling for detail work, and "one page at a time" signals the paginated listing mode. There is no explicit when-not-to-use or prerequisite context, but the alternative is named and its selection condition is clear.

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