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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower, yet the description still adds two pieces of context: the required auth scope and a negative disclosure that provider identifiers, cursors and error text are never returned. That last point is genuinely useful because it tells an agent this result cannot be used to diagnose sync failures.

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?

Two short sentences, no filler. The subject of the response is front-loaded, followed by the permission requirement and the exclusion note in descending order of importance.

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 and no parameters, the description carries the return-shape burden and does so adequately by naming the entities and the sync-status field plus what is omitted. Minor gap: it does not hint at whether an empty connection list is a normal state or what the sync-status values can be.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly stays silent on inputs rather than inventing filtering options.

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?

Names the specific resource (connected point-of-sale and catalog sources) and the key derived attribute (whether each is syncing), scoped to the merchant. It does not explicitly differentiate itself from related siblings such as get_connection_link, but the resource is unmistakable.

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?

'Requires connections:read' gives a prerequisite, which implies this is the read path for inspecting connection state. However, there is no explicit statement of when to use this versus get_connection_link or get_action_status, and no exclusions are offered.

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