Refresh Map

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

With no annotations, the description carries the full burden, but it only says 'Refresh map data' without disclosing side effects, idempotency, data source behavior, or what triggers an actual update. The UI-call hint provides limited behavioral context but not enough for an agent to predict side effects.

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 a single, front-loaded sentence with no redundant filler: 'Refresh map data' first, then the UI context. It is appropriately short, though the minimalism borderlines on under-specification.

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?

Given there are no annotations, the description omits important behavioral and parameter details that an agent would need to invoke and use the tool confidently. The existence of an output schema helps, but the city parameter's role and the effects of refreshing are still undefined.

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 description does not mention the optional city parameter at all, and schema description coverage is 0%, so the description must compensate but does not. The parameter name 'city' and its null default are visible in the schema, but their meaning for refresh behavior is left entirely to inference.

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 phrase 'Refresh map data' names both the action and the resource clearly, and '(called from UI)' adds a context cue about how it is triggered. However, it does not differentiate this from the many sibling refresh_* tools beyond the resource name.

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?

The description only notes that this is called from the UI, giving an implicit usage context but no explicit when-to-use guidance. It does not mention alternatives or state when not to invoke this tool, which is especially relevant among the large refresh_* sibling family.

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