get_tracked_changes

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

The description explains the output format and ordering but does not explicitly state that it is a read-only operation (no side effects). With no annotations, this leaves some ambiguity about whether calling this tool might modify state, though the name 'get' implies safety.

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?

Two short sentences front-load the core action and output details. Every sentence adds value without redundancy.

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?

While the tool is simple and has an output schema, the complete lack of parameter documentation and usage guidance leaves gaps. The description covers the basic purpose and return format but fails to fully equip the agent for correct invocation.

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 only parameter, document_handle, is not mentioned in the description. With 0% schema description coverage, the agent has no guidance on what this parameter does or its expected values, severely hindering correct usage.

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 tool returns 'all pending tracked changes' as a JSON list, specifying the fields included. It distinguishes itself from sibling tools (accept/reject changes) by focusing on retrieval, though it does not explicitly contrast them.

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 is provided on when to use this tool versus alternatives like accept_all_changes or reject_change. The description only states what it does, leaving the agent to infer usage context from the sibling list.

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