refresh_data

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

With no annotations, the description carries full burden. It discloses bypassing the normal refresh throttle, a key behavior. However, it does not mention potential side effects like rate limiting or whether the refresh is per-user or global. Additional behavioral context would improve transparency.

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 short sentences with no extraneous words. The first sentence defines the core action, the second adds usage guidance. Perfectly front-loaded and efficient.

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 tool with no parameters and an output schema, the description covers purpose, usage context, and a behavioral trait. It lacks details like confirmation of success or failure handling, but overall is thorough enough for an agent to use correctly.

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 input schema has zero parameters, so baseline is 4. The description adds value by explaining what the tool does (forces refresh of all cached data) beyond the empty schema, making the semantics clear.

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 tool forces an immediate refresh of all cached Anker Solix data (sites, devices, energy) bypassing the throttle. This is a specific verb+resource combination with clear scope, distinguishing it from sibling read-only 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?

Explicitly says to call when suspecting stale data, e.g., after changing settings in the Anker app. This provides clear context for use, though no explicit alternatives are mentioned, but siblings are all read functions, making this the sole refresh tool.

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