compatibility_changesReturn cursor-paginated, approved ResolveMesh compatibility events using the same allowlisted filters as the public JSON API.
| Name | Required | Description | Default |
|---|---|---|---|
| tool | No | ||
| limit | No | ||
| since | No | ||
| client | No | ||
| cursor | No | ||
| severity | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the description must add behavioral context. It adds that the result is cursor-paginated and uses allowlisted filters, but does not disclose any additional behavioral traits like rate limits or authentication requirements. Consistent with 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?
Single sentence front-loads key attributes (cursor-pagination, approved, filters) with no wasted words. Succinct and to the point.
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?
Despite having 6 parameters with no schema descriptions and no output schema, the description is too brief. It does not explain how pagination works, what the filters do individually, or what the return format looks like. For a moderately complex tool, this leaves significant gaps for the agent.
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 0%, so the description should compensate for all 6 parameters. It mentions 'allowlisted filters' and 'cursor-paginated', which vaguely covers some parameters, but most (tool, limit, since, client, severity) are left unexplained. The description adds little meaning beyond the schema's enum values and constraints.
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?
Title and description clearly state the tool lists approved compatibility changes with cursor-pagination. The phrase 'approved ResolveMesh compatibility events' and reference to the public JSON API distinctively set it apart from the sibling 'compatibility_lookup', which likely serves a different lookup purpose.
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 implies this tool is for listing approved events with specific filters, but it does not explicitly state when to use it versus the sibling tool 'compatibility_lookup'. No guidance on prerequisites or context where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The two tools have clearly distinct purposes: one provides a paginated list of approved compatibility events, the other gives a specific lookup for a client-tool pair. No overlap.
Both tool names follow the consistent pattern 'compatibility_<verb>', using snake_case. 'changes' and 'lookup' are verbs that clearly indicate their actions.
With only 2 tools, the surface is minimal but appropriate for a niche domain like 'ResolveMesh Compatibility Intelligence'. It slightly underrepresents possible operations but remains reasonable.
The set covers key operations: retrieving recent changes and performing a single lookup. Minor gaps exist, such as bulk lookup or listing all supported pairs, but they are not critical for the core functionality.