render

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that ParaView runs headless and that the result is an image plus metadata, but says nothing about execution cost, latency, or prerequisite state (e.g. requiring completed simulation data).

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 tight sentence, front-loaded with the action and ending with the observable result. No filler or restatement of the name.

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 21-parameter rendering tool with no output schema, the description is adequate but thin. It covers what the tool produces but not the prerequisites, the image format/location, or how the mode-dependent parameters combine, leaving the agent to reconstruct the workflow.

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?

With 21 parameters and only 67% schema description coverage, the description carries a compensation burden and contributes zero parameter meaning. It does not clarify the mode/field/patches interplay or any of the undocumented parameters (width, height, iso_value, seed points, contour_field).

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 (render) and resource (flow/mesh picture via headless ParaView) plus the return type (image plus metadata). It is clearly distinguishable from siblings like post_process or field_stats, though it never names an alternative explicitly.

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?

No when-to-use guidance at all: nothing says whether the case must already be solved, how this relates to post_process or field_stats, or when rendering is or isn't appropriate. The agent must infer the workflow context.

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