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

The description discloses important behavioral details: it iterates through every connected provider, can exceed timeout, and work continues server-side even if the client times out. The annotations are not contradicted, though the description could more explicitly state whether it writes data locally or only fetches.

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?

The description is concise and well-structured: action, purpose, return type, and a clear timeout note are all included without unnecessary fluff.

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?

The description explains what it returns ('per-app sync results') and the timeout behavior, which is sufficient given there is no output schema. It could be slightly more specific about the shape of the per-app results, but this is not a significant gap.

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 has no parameters and the description correctly does not invent any. With zero parameters, the baseline of 4 applies and no additional param explanation is needed.

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 clearly states the action ('Refresh data from all of the business's installed integrations now') and specifies what it pulls ('latest transactions/records from each connected app'). It is distinct from related tools like refresh_business_data by focusing on installed integrations.

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?

Provides explicit guidance on when to use the tool and what to expect: it can take longer than a typical timeout, may continue server-side after timeout, and advises re-reading data (e.g., list_expenses) instead of retrying. This is strong practical usage direction.

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