list_changes

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

Annotations already mark this as read-only and non-idempotent, but the description adds crucial behaviors beyond that: ordering by seq ascending, the need to page through with since until next_since is null, and the default exclusion of routine records. This is exactly the kind of context an agent needs and is not present in the schema or annotations.

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?

Every sentence earns its place: purpose, pagination, alternatives, filters, and key fields are all covered in a compact block. It is dense but not bloated, with the most important operational detail (oldest-first, must page) placed early.

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 read-only sync tool with no output schema, this description is unusually complete. It covers ordering, pagination, default exclusions, field-level guidance (applies_if, matter_key), and points to get_matter for expansion. The agent has everything needed to select and use the tool correctly.

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?

Although the schema already covers all five parameters (100% coverage), the description adds meaning: bucket/family dimensions are explained semantically, since is tied to the returned next_since cursor, and project is illustrated with examples. This goes well beyond the baseline for high schema coverage.

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 names a specific resource ('release changes for CNCF/cloud-native projects') and a specific operation mode ('Incremental SYNC feed'), clearly distinguishing it from the query-oriented siblings like list_releases and get_release. It also clarifies the core use case: keeping a local copy up to date.

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?

It explicitly states when to use this tool (incremental sync) and when not to ('what is the latest release of X' → use list_releases or get_release). It also explains the pagination pattern and filter semantics, giving the agent actionable guidance for invoking it correctly.

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