physics_setup_flow_boundaries

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

With no annotations provided, the description carries the full burden of disclosure. It does not mention side effects (e.g., overwriting existing boundaries), required permissions, or validation behavior. The return value is vaguely described as 'Configuration confirmation' without specifics.

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 well-structured with a clear first sentence, a brief explanation, an Args list, and a Returns note. It is concise and front-loaded, though the Args section largely repeats parameter names without much additional context.

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 6 parameters, no output schema, and no annotations, the description covers inputs and basic functionality but lacks critical context like prerequisites (physics interface must exist), validation rules, and error handling. It is adequate but not fully comprehensive.

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 the description includes an 'Args' section explaining each parameter, including default values for 'inlet_velocity' and 'outlet_pressure'. This adds significant meaning beyond the bare schema, though it could clarify units and acceptable value formats.

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 sets up Laminar Flow boundary conditions with inlet velocity and outlet pressure. It uses specific verbs ('Setup', 'configures') and distinguishes from sibling tools like 'physics_interactive_setup_flow' and 'physics_setup_heat_boundaries' by specifying the physics type and purpose.

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 provides no guidance on when to use this tool versus alternatives like 'physics_interactive_setup_flow' or 'physics_boundary_selection'. It does not mention prerequisites (e.g., a Laminar Flow physics interface must be added first) or scenarios where this tool is appropriate.

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