refresh_data

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

With no annotations at all, the description carries the full behavioral burden. It does disclose the side effect (cache clearing plus a network re-fetch of account state), which is the most important trait, but says nothing about cost/latency, failure behavior, whether cached data is recoverable, or whether the operation is safe to call repeatedly.

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: the action first, the trigger second. No filler, no restatement of the tool name, and the most decision-relevant information is front-loaded.

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 zero-argument tool with no output schema and no annotations, the description covers what it does and when to invoke it. The remaining gap is operational: no indication of latency, failure modes, or what the caller should do with the refreshed state, which matters for a cache-invalidating network call.

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 schema has zero parameters, so there is nothing to disambiguate; the baseline for a no-param tool applies. The description correctly implies the operation is unscoped and takes no arguments.

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 two specific actions on a specific resource: clearing Renpho auth/measurement caches and re-fetching account state. This is clearly distinguishable from the read-only get_* siblings, though the description never names a sibling or explicitly contrasts itself with get_current_user, which also surfaces account state.

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?

"Useful after taking a new measurement or after the mobile app syncs" gives concrete triggering conditions, which is stronger than most cache-refresh tools. It gives no when-not guidance (e.g., don't call mid-sync or repeatedly, since it is a network re-fetch), leaving the exclusion side to inference.

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