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

The description accurately reflects a read-only fetch operation with pagination, matching the readOnlyHint=true annotation and destructiveHint=false. It mentions following has_more and retaining the cursor, which are key behavioral traits, though it does not detail error scenarios or output structure beyond that.

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 extremely concise and contains no redundant or irrelevant information. Every clause contributes to understanding the sync and pagination behavior, making it efficient and well-structured.

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?

Given there is no output schema, the description still provides essential operational context: changes are bounded, pagination uses has_more, and the cursor must be retained. It is sufficient for basic usage, though it could mention response fields or error conditions more explicitly to be fully complete.

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?

All six parameters are described in the schema, and the descriptions add practical meaning beyond basic types, such as cursor handling ('Copy returned next_cursor unchanged') and max_tokens budget ('Increase on BUDGET_TOO_SMALL'). This goes beyond the schema but does not deeply elaborate on every parameter.

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 clearly states the action ('Fetch bounded changes and tombstones') and the cursor-based pagination mechanism. It effectively conveys the tool's purpose for syncing incremental changes, though it does not explicitly contrast with similar sibling tools like get_space_changes.

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 provides no guidance on when to use this tool versus alternatives such as get_space_changes or list_knowledge_changes. The intended usage must be inferred from the tool name and the cursor/sync terminology, but no explicit direction is given.

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