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

The readOnlyHint annotation already establishes that this is a safe read operation, lowering the burden on the description. The description adds useful behavioral context by saying it returns 'summaries' in reverse chronological order, but it omits pagination behavior and anything about how recent runs are selected.

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 the core purpose, followed by concrete usage examples and the return ordering. Every sentence contributes information without repetition or filler.

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?

The description tells an agent what the tool lists and in what order, which is useful for a read-only list endpoint. However, with no output schema and 0% schema description coverage, it leaves pagination and summary contents underspecified for fully confident 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?

Schema description coverage is 0%, so the description must carry the burden for three parameters. It only implicitly covers syncId through 'for a sync process' and gives a vague sense of 'recent' and ordering, while the limit and before/pagination parameters are never explained.

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 states a specific verb and resource: 'List recent sync run summaries for a sync process.' The word 'summaries' distinguishes it from sibling get_sync_run, which presumably returns one detailed run, and 'sync process' scopes it away from list_syncs. An agent can identify the correct operation without opening the schema.

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?

The description provides concrete example questions it is meant to answer, making the intended usage context clear. It does not mention when not to use it or explicitly point to alternatives like get_sync_run for detailed data, but the positive use case is well specified.

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