Refresh account snapshot

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

Annotations already state readOnlyHint=false, openWorldHint=true, and destructiveHint=false, and the description usefully clarifies that the external API calls are read-only while the tool writes a local snapshot. It also discloses demo-mode behavior and what gets loaded, but it does not cover authentication needs, rate limits, failure modes, or snapshot storage 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?

The description is two tightly written sentences with no wasted wording. The main action is front-loaded, and the demo-mode note is placed after the core behavior.

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 tool with no output schema, the description covers the core behavior, the local snapshot outcome, change reporting, and demo mode. It leaves some operational details unstated, such as where the snapshot lives and how results are returned, but it is substantially complete for selection and invocation.

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 only 50%, with demo undocumented in the schema and platform described only as 'Which platform.' The description compensates by explaining demo: true as loading the fictional Fernbrook Market demo account, while platform semantics are left mostly to the enum values.

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 gives a specific verb and resource: pull campaigns, journeys, segments, templates, and content blocks into a local snapshot, then report changes. It is clear enough to distinguish from most siblings, though the final 'report what changed' phrase overlaps slightly with the sibling tool what_changed.

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?

It gives one concrete usage detail: set demo: true to load the fictional Fernbrook Market demo account. It does not explicitly say when to use refresh_account versus what_changed, connection_status, or other related sibling tools, so the agent must infer the workflow context.

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