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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing what data each entry carries, including next_run_at and run statistics, which is behaviorally useful given there is no output schema. It stops short of any behavioral detail such as ordering, pagination, or whether stats are aggregated or per-run.

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 compact sentence that front-loads the resource and then lists the fields with zero filler. It is a fragment without a predicate, which slightly weakens the opening but wastes no words.

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 input parameters and no output schema, the description correctly spends its words on the returned field set, which is exactly the gap an agent would otherwise face. Nothing about filters, ordering, or scope (all users vs current user) is stated, but for a zero-argument read tool this is close to sufficient.

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. No false parameter expectations are created.

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 the resource (regular/periodic syncs) and enumerates its fields (name, route source→target with cloud names, frequency, direction, is_active, next_run_at, run stats), which makes the tool's subject unmistakable and separable from create/update/delete/run_scheduled_sync siblings. It is a noun phrase with no explicit verb such as 'list' or 'returns', so the read action is only implied by the tool name and the field enumeration.

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 when-to-use guidance, no mention of alternatives (e.g. list_transfers for one-off transfers, get_usage for quotas), and no exclusions. The agent must infer that this is the read path for scheduled syncs purely from the enumeration of returned fields.

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