list_changesets

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

With no annotations, the description must carry the behavioral disclosure, and it does add one key behavior: 'limit/offset paginate — this returns one bounded page, not the full table.' This alerts the agent that pagination is required for full results. However, it omits other relevant behaviors such as whether results are sorted, whether filters (state, developer, timeframe, application) combine with AND, and any rate limits or read-only guarantees. A score of 3 reflects that it adds some value but is far from comprehensive.

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 sentences, zero wasted words. The purpose is stated first, and the critical pagination caveat is front-loaded immediately after. This is an exemplar of concise, structured description.

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 tool with 7 parameters, no output schema, and no annotations, the description is drastically under-specified. It covers only pagination, not the semantics of the filters, default sorting, output format, or any constraints like authorization. An agent would be unable to reliably construct a correct call without inspecting the schema (which is also sparse) or making assumptions. The description is insufficient for the tool's complexity.

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 14% (only 'query' has a description). The tool description mentions 'limit/offset' but does not explain any of the other five parameters. There is no compensation for the undocumented parameters, leaving the agent to guess the meaning and acceptable values for state, developer, timeframe, and application. The description adds minimal value beyond the schema's own limit/offset defaults.

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 specific verb and resource: 'List changesets (update sets).' It also clarifies the pagination behavior, which distinguishes it from related tools like get_changeset_details (which focuses on a single changeset) and mutation tools (update_changeset, commit_changeset, etc.). The purpose is unambiguous and well-scoped.

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 gives no explicit guidance on when to use this tool versus alternatives. It does not mention that for detailed views of a specific changeset one should use get_changeset_details, or that mutation tools are for modifications. The only implicit guidance is 'list' suggests a read operation, but there is no direct routing or context about selection criteria.

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