get_tracked_changes

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

Describes return format and ordering, but with no annotations, fails to mention that this is a read-only operation with no side effects, or what happens when no changes exist. Basic transparency but lacking safety expectations.

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?

Three sentences, front-loaded with purpose, efficient. Could be slightly more structured but overall concise.

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 the simplicity (1 optional param, output schema exists), the description explains output well but neglects input parameter entirely. Missing usage context, but adequate for basic retrieval.

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 'document_handle' is entirely undocumented in both the schema (0% coverage) and the description. The description does not explain how to specify which document, leaving the agent to guess.

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?

Clearly states it returns all pending tracked changes as a JSON list, specifying content type (insertions/deletions) and return order. Distinguishes from sibling accept/reject tools by its read-only retrieval 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?

No guidance on when to use this tool versus accepting or rejecting changes, nor any prerequisites like having track changes enabled. Agent must infer usage from context.

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