Render model views without desktop access

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

Annotations only declare the safety flags (readOnlyHint=false, idempotentHint=false, destructiveHint=false); the description adds genuinely new context: output format is a PNG (drawing, not screenshot), the file is saved to Documents/ETABS-MCP/exports, the filename is unique per call (which explains the non-idempotent hint), and no UI interaction occurs. It stops short of describing failure behavior (e.g., plan without a story) or whether the response returns the path.

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 output format and the no-screen-access guarantee are front-loaded, followed by the view/story rule and the file-save detail. The closing sentence listing clicks, keys, focus, menus, and native window changes is slightly redundant with 'no screen access' but reinforces a key constraint, so it roughly earns its place.

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 5-parameter tool with no output schema, the description covers the core behavior and side effect (file written to a known folder) well. It leaves gaps on three undocumented parameters, on what the call returns (path? inline image?), and on error conditions, which are material for correct 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 description coverage is 0%, so the description carries the full burden, yet it only explains 'view' (3d/plan/elevation) and 'story'. The 'width', 'height', and 'instance' parameters — including the instance selector for multi-instance setups — are given no meaning in either schema or description.

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 specific verb+resource ("Generate and return a PNG from ETABS API geometry") and explicitly distinguishes the output from screenshots. An agent can tell this apart from get_model_geometry (raw geometry data) and from any window-based rendering, especially given the title's 'without desktop access' framing.

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 conditional parameter guidance ("For a plan specify an exact story such as Story3") and enumerates the valid view kinds, which is useful. However, it never states when to choose this tool over siblings like get_model_geometry or execute_code, nor any prerequisites or exclusions. Usage is implied, not routed.

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