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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations do not carry: the existing ten-minute background collection and the five-minute per-workspace rate limit, which explains why an apparently non-read-only fetch call is throttled.

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 well — the action, the caveat, then the limit. However the French sentence fully restates the English content with no additional information, consuming roughly a third of the text without earning its place for an agent reader.

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 output schema and a single parameter, the description supplies the essentials an agent needs: what triggers the call, what not to do, and the throttle. It does not say which connected accounts are covered or what the response contains, but those gaps are minor for a one-parameter refresh tool.

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?

One required parameter (workspace_uuid) with 0% schema description coverage, so the description must compensate. It conveys the workspace-scoped nature via 'one call per workspace', but never states what the identifier is or where to obtain it; the parameter's meaning is largely carried by its self-explanatory name.

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 ('Fetch the newest comments and messages from the connected accounts') with the scope 'right away' that marks it as an on-demand pull rather than a listing. It does not explicitly name the sibling it contrasts with (list_inbox / get_inbox_thread), so an agent must infer the boundary from the timing language.

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?

Explicit when-to-use and when-not-to-use: 'The collection already runs every ten minutes, so use this only when waiting is not acceptable.' It also gives the rate-limit condition (one call per workspace every five minutes), so the agent knows both the trigger and the throttle before invoking.

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