Sync Conflicts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it does not resolve conflicts or start network sync, confirming and supplementing annotations. It also clarifies it deals with locally tracked requests, adding context beyond 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?

The description is three sentences: purpose, usage context with alternatives, and behavioral notes. No redundant or unnecessary words; every sentence earns its place.

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 simple single-parameter input, full annotations, and presence of an output schema, the description sufficiently explains the tool's role in a workflow (after sync_monitor, before sync_resolve_conflict). It mentions the data source (locally tracked) and explicitly states what it does and does not do.

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 'limit' has full schema coverage (100%) with detailed description. The tool description does not add additional parameter information beyond what's in the schema, so baseline 3 is appropriate.

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 lists locally tracked requests with offline sync metadata marked as conflict. It uses specific verbs and resources, and distinguishes from sibling tools like list_requests and sync_resolve_conflict.

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?

Provides explicit guidance: use after sync_monitor shows conflict>0 to obtain IDs, and offers alternatives (sync_resolve_conflict to clear, list_requests for all requests). This gives clear when-to-use and when-not-to-use context.

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