Review Sync Evidence

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-structured context: every match must be selected, conflicting matches are blocked from approval, and the tool performs no audio analysis or calibration. It does not explain the review-revision/conflict-recovery behavior, but the schema does.

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 tightly packed sentences: purpose first, then the decision constraint, then the negative scoping. No filler, no repetition of the title, and the most consequential rule (matches require selection, conflicts cannot be approved) is front-loaded.

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?

With a full output schema and 100% parameter coverage, the description only needs to convey intent and constraints, which it does. The one thing left entirely to the schema is the revision handshake (expected_review_revision required on subsequent selections), which is material to correct invocation but adequately documented there.

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 description coverage is 100% and every parameter (matches, estimates, confidence, selected_ids, rejected_ids, expected_review_revision, tolerances) is documented in the schema itself. The description echoes concepts like offset, confidence and method agreement but adds no syntax, format or default detail beyond what the schema provides, so the baseline 3 applies.

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 names a specific verb and resource ('Review caller-supplied camera/recorder offset estimates') and enumerates the review criteria: independent-method agreement, confidence, and conflicting alternatives. It also distinguishes itself from adjacent concerns by explicitly disclaiming audio analysis, confidence calibration, and Premiere synchronization, so an agent can tell what this tool is and is not.

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?

It states a clear operating condition ('All matches require selection') and a hard constraint ('conflicting matches cannot be approved'), plus negative scoping ('Does not analyze audio, calibrate confidence or synchronize Premiere'). What is missing is an explicit statement of when to reach for this tool versus, say, the capture/analysis steps that produce the estimates it reviews.

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