list_changesets

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

Adds one behavioral trait (prerequisite) beyond annotations. Does not describe pagination, ordering, or output format. Annotations already provide readOnlyHint and openWorldHint.

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?

Single sentence, front-loaded, no unnecessary words.

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?

Lacks output format description. For a list tool without output schema, more detail on returned data would improve completeness. Schema partially compensates.

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 provides 100% coverage with parameter descriptions. Description adds no additional parameter information, so baseline score of 3 is appropriate.

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?

Verb 'List' and resource 'update sets (changesets)' are clear. Clarifies that update sets and changesets are the same. However, sibling 'list_update_sets' exists without differentiation.

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?

Only provides a prerequisite ('requires SCRIPTING_ENABLED=true'). No guidance on when to use vs alternatives like 'get_changeset' or 'list_update_sets'.

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