list_sync

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

Annotations already disclose the readOnlyHint, openWorldHint, idempotentHint, and destructiveHint profile, so the description is not the sole carrier of behavioral information. It adds the HTTP endpoint 'GET /sync', but little other behavioral context beyond that.

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 extremely short and front-loaded, containing only a one-line purpose and the endpoint. Nothing is padded, and for a trivial no-parameter tool, this is an appropriately sized definition.

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 tool is a simple read with 0 parameters, annotations carry the behavioral profile, and an output schema exists so return values need not be described. The description is minimal but sufficient; the only gap is clarifying the exact scope of 'sync status'.

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 tool has zero parameters, so there is nothing for the description to explain beyond the schema. With no parameters, the baseline of 4 is appropriate and no additional semantic burden exists.

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 verb and resource ('Get Sync Status') plus the endpoint 'GET /sync', so the basic intent is recognizable. However, it is vague about what 'sync status' contains and does not distinguish this from sibling tools such as list_sync_items and list_sync_queue.

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 guidance on when to call this tool versus alternatives like list_sync_items or list_sync_queue, nor any exclusions or prerequisites. The description simply states the endpoint with no contextual decision support.

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