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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description usefully adds that the response contains per-event-type counts (created, updated, deleted, skipped, reconciled) and error codes, which partially compensates for the absent output schema, but says nothing about auth needs, pagination, or error behavior.

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?

A single well-formed sentence that front-loads the verb and resource. No filler or redundancy, though it is lean enough that it omits needed detail rather than being padded.

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 no output schema the description does convey the shape of the returned data, which is the right focus. However, for a 2-parameter tool at 0% schema coverage it omits any parameter explanation and any sibling differentiation, leaving real gaps.

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 0% for both required parameters (syncId, runId), and the description does not explain either one. It only implies that a run is identified, leaving the description unable to compensate for the schema gap.

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?

States a specific verb ('Get') plus resource ('a single sync run') and enumerates the returned content (per-event-type counts, error codes). The 'single' wording implicitly distinguishes it from list_sync_runs, though no sibling is named explicitly.

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?

There is no statement of when to use this tool versus list_sync_runs, get_sync, or get_sync_health, and no prerequisites or exclusions. The only hint of usage is that a single run is addressed, which an agent must infer from the existence of a runId parameter.

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