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

Annotations mark this non-read-only, non-idempotent and open-world, and the description corroborates all three: it discloses a hard rate limit (10/day per list), that new entries arrive per the list's policy, and that nothing is removed (consistent with destructiveHint=false). It stops short of saying what permissions or list states cause a failure.

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 compact sentences with the action first, the rate limit parenthetically attached, and the side-effect guarantee last. Nothing is padded or repeated from the schema.

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?

For a two-parameter trigger tool with no output schema, the description covers the action, its limit, and its side effects. The one gap is the response: it does not say whether the call reports newly fetched entries or just success, which an agent polling for results would want to know.

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%, so both parameters, including the policy enum and its semantics, are already fully documented in the schema. The description only echoes the policy concept ('new entries arrive by the list's policy') without adding syntax or edge-case behavior, so the baseline 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 and resource ('read a connected list's source again now'), which is meaningfully distinct from siblings like list_sources or get_list. It never names an adjacent tool to route against, so differentiation is left to the reader.

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 'again now' phrasing implies this is a manual refresh of an already-connected source, and the daily cap signals it is a rate-limited poll rather than a routine read. There is no explicit when-not guidance or named alternative (e.g., list_sources to obtain the id), so usage is inferred rather than stated.

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