physics_interactive_setup_heat

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

No annotations provided; the description does not clarify whether the tool is read-only or modifies the model. It mentions both 'identify and configure' and 'provides setup instructions,' creating ambiguity about 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 concise, uses bullets and clear sections (Args, Returns), and contains no unnecessary text.

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?

Covers the main purpose but misses prerequisites (e.g., need for an active model) and does not detail the return format or interactive behavior thoroughly.

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 0% schema coverage, the description adds basic meaning for physics_name and model_name but lacks examples or format constraints, leaving gaps.

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 description clearly states it is an interactive setup wizard for Heat Transfer boundary conditions, listing steps and distinguishing from related tools like physics_setup_heat_boundaries.

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 explicit guidance on when to use this tool vs alternatives like physics_setup_heat_boundaries or physics_add_heat_transfer. The context hints at an interactive role but lacks direct usage instructions.

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