syncpen_recent_changes

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

No annotations exist, so description carries full burden. Discloses inclusion of human edits and agent/API writes, and ordering by time. Lacks details on output format, pagination, or read-only nature, leaving some ambiguity.

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?

Extremely concise—two sentences that front-load the main purpose then provide usage guidance. Every sentence is informative with no fluff.

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 no output schema, the description gives a reasonable high-level picture of return content (who, what, when). Could be slightly more explicit about output structure (e.g., array of change objects), but considering the simplicity, it is mostly 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?

Schema already covers all 3 parameters with 100% description coverage. The description adds value by explaining usage context (e.g., passing 'since' to catch up, scoping to folder), beyond the schema's basic parameter descriptions.

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 it's a 'time-ordered feed of recent workspace changes' with specific verb and resource. It distinguishes from sibling tools like list_documents or list_folders by focusing on changes rather than current state.

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?

Explicitly advises using it to 'catch up on what changed since you last looked' or 'scope to one folder'. Mentions using the `since` parameter. Does not explicitly contrast with sibling tools but context is sufficient.

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