List changes

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not say what a "change" is, whether results are paginated, whether authentication is required, or what the return shape looks like.

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 words is not conciseness but under-specification. Nothing is front-loaded because nothing is said; the brevity here reflects missing content rather than efficient prose.

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 a complex nested parameter object, no annotations, no output schema, and 0% schema coverage, the description is completely inadequate. An agent cannot infer filtering, paging, or sorting behavior from "List changes."

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 single parameter is a nested list_info object with 0% schema description coverage, containing seven undocumented sub-fields (row_count, sort_field, sort_order, start_index, fields_required, get_total_count, search_criteria). The description contributes zero meaning to any of them.

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?

"List changes" is a tautological restatement of the tool name and title. It gives an agent no scope, no filtering semantics, and no differentiation from the many sibling list_* tools or from get_change.

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?

There is no indication of when to use this tool versus get_change, list_requests, or any other sibling. No prerequisites, no context, no exclusions are stated.

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