list_changesets

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to restate safety. It adds the requirement that SCRIPTING_ENABLED must equal true, which is useful behavioral context. However, it does not describe output format, pagination, or error behavior, which would enhance transparency further.

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 a single succinct sentence that conveys the core purpose and a key requirement. There is no redundant information, and every word contributes meaning.

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?

For a simple read-only list operation with schema-documented parameters, the description covers the essentials. However, the conflation of 'update sets' and 'changesets' alongside the sibling 'list_update_sets' creates ambiguity about scope, and the description does not clarify the relationship between these concepts.

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% description coverage for its two parameters ('limit' and 'state'), so the schema already provides full parameter semantics. The description adds nothing beyond the schema, which aligns with the baseline score of 3.

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 states a clear action: 'List update sets (changesets)', with the verb 'List' and resource 'update sets'. However, it does not differentiate from the sibling tool 'list_update_sets', which likely serves a similar purpose, so it falls short of a 5.

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 mentions a prerequisite ('requires SCRIPTING_ENABLED=true'), but provides no guidance on when to use this tool versus alternatives like 'list_update_sets' or when not to use it. There is no mention of context or exclusions, leaving the agent without decision-making information.

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