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

Annotations already declare idempotentHint=true, destructiveHint=false, openWorldHint=true and readOnlyHint=false, so safety is largely covered. The description adds the timing purpose but does not disclose what the sync mutates locally, its cost/latency, or auth needs. There is mild tension between the 're-read' framing and readOnlyHint=false, though sync tools plausibly write local state, so this is not a true contradiction.

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 tight sentences: purpose first, then the usage trigger. Nothing is padded and every clause carries information.

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 simple two-parameter, zero-required sync tool with annotations and no output schema, the description covers what it does and when to call it. It omits only minor details (what the refresh returns, workspace inference), which the schema already handles.

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 workspaceId and idempotencyKey are fully documented in the schema, including the workspace-inference rule and retry semantics. The description adds no parameter meaning beyond that, 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 and resource: 'Re-read the accounts from the networks', which distinguishes it from passive listers like list_accounts by implying a network sync. It does not explicitly name a sibling, but the sync/refresh framing is clear enough to separate it from read-only listing tools.

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 trigger: 'Use it right after someone has connected one, so it appears without waiting.' This tells the agent the exact moment to invoke it. It stops short of naming alternatives or when-not-to-use (e.g. vs list_accounts), so it is not a full 5.

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