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

Goes well beyond the annotations: it states the return contract (synced:true, or synced:false with the feed's error), that errors are reported rather than thrown, that screens are notified on success, and the required permission (integration.edit at the data source's location). These are exactly the mutation-side effects an agent needs and that readOnlyHint/destructiveHint do not convey.

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?

Front-loaded with purpose, then return semantics, alternative, and permission — every clause earns its place. The first sentence is dense and runs long, which slightly hurts scanability, but nothing is redundant.

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?

Covers purpose, scoping to a single feed, the alternative tool, error behavior, side effects on screens, and required permissions. An output schema exists so return values need not be spelled out further; nothing needed to call it correctly is missing.

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 coverage is 100% and the single dataSourceId is fully documented in the schema (ds_… from list_items kind data_sources). The description implies the id refers to one feed but adds no new format or constraint detail, so the baseline of 3 applies.

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+resource with scope: 'Pull fresh data through one connected feed ... now, instead of waiting for its scheduled sync.' It explicitly distinguishes itself from the sibling refresh_all_data_sources, so an agent can choose between them without opening either 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?

Gives an explicit when-to-use ('now, instead of waiting for its scheduled sync') and names the alternative with its selecting condition ('To sync every feed at once use refresh_all_data_sources'). Routing between the two sync tools is unambiguous.

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