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

Discloses polling up to 60s, return fields, error states (needs_action with reconnect_url), and non-destructive nature. Annotations are minimal, so description carries burden. Lacks rate limit or side-effect details.

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?

Single paragraph, dense but readable. Front-loads action and mechanism. Could be slightly more scannable with structuring, but no wasted sentences.

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?

No output schema, yet description fully explains return object (status, executionStatus, lastUpdatedAt, synced, needs_action, reconnect_url, timed_out) and how to handle each case. References sibling tool for re-check.

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?

Provides meaning beyond schema: items as array of selectors (optional), wait as toggle for synchronous vs fire-and-forget. Schema has 0% description coverage, so description compensates well.

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?

Clearly states the action ('forces re-sync'), the resource ('bank connections'), and the mechanism (PATCH + poll). Distinguishes from siblings like openfinance_get_item_status.

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?

Explicitly states when to use (stale data), what not to do (no disconnect), alternatives (openfinance_get_item_status for timed_out), and both modes (sync all vs specific items, wait:false for fire-and-forget).

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