physics_set_material

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It only states the action and return value ('Assignment confirmation'), but fails to mention side effects (e.g., overwriting previous assignments), required permissions, or whether the operation is reversible. The description is minimal.

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 very concise: one line for purpose, then a bullet list for parameters, and a returns line. No extra information or fluff. Everything 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?

Given the tool has 4 parameters, no output schema, and no annotations, the description is somewhat adequate but lacks depth. It covers the basic action and parameter semantics but omits error conditions, prerequisites, and detailed behavior. For a simple assignment tool, it meets minimum viability.

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 coverage is 0%, so the description must compensate. The 'Args' section describes each parameter: 'physics_name' and 'material_name' as names, 'domain_selection' as domain numbers with default, and 'model_name' with default. This adds meaning beyond the schema, though more detail on domain selection format would improve it.

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 the tool's action: 'Assign a material to physics domains.' The verb 'assign' and the resource 'material' are specific, and the tool is distinct from siblings like 'physics_add' or 'physics_configure_boundary' which handle different aspects of physics setup.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The purpose is clear, but usage context (e.g., requires existing physics interface, should be called after adding physics) is only implied.

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