etabs_refresh_view

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

With annotations already declaring readOnlyHint=false and destructiveHint=false, the description adds the context that this is a post-mutation UI sync ('after model changes made through the API'), explaining why it is not a read-only call. It does not explain why idempotentHint=false (presumably the zoom_to_fit toggle) or what state is affected, so it only partially earns credit beyond the annotations.

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?

A single sentence with no wasted words, and the core action is front-loaded before the optional modifier and the trigger condition.

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 one-parameter UI-sync tool with annotations and an output schema present, the description covers what it does, when to call it, and the one option. A note on whether it must precede screenshot/render_view calls would make it fully self-sufficient.

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 description coverage is 0%, but there is only one parameter and the description explicitly names it as an option ('and optionally zoom to fit'), clarifying that the view redraw happens regardless while the zoom is conditional. It does not state the default (true), which the schema carries, nor any side effect of zooming.

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 concrete verb and resource ('Redraw the ETABS model views') plus an optional mode ('zoom to fit'), which is more specific than the title. It partially distinguishes itself from UI-adjacent siblings like etabs_render_view and etabs_screenshot, but does not explicitly say how it differs from them.

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?

'after model changes made through the API' gives a clear trigger condition, which is genuinely useful timing guidance. However, it never states when *not* to call it, nor names an alternative such as etabs_render_view for fresh renders, leaving the agent to infer the routing.

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