apply_material

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

With no annotations, the description carries the full burden. It does disclose the material type ('Standard'), the optional disk-read side effect of loading a bitmap, and the assignment action. However, it does not state that assigning replaces any existing material on the objects, whether new material instances are created per call, or what happens on invalid handles — meaningful gaps for a mutating tool with zero annotation coverage.

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 clean sentence that front-loads the core verb and resource, with the optional-texture detail tucked into a parenthetical that earns its place. No filler or redundancy; slightly dense but efficient and well ordered.

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 three parameters at 0% schema coverage, no annotations, and no output schema, the description is too thin. It omits material_name semantics, overwrite behavior, handle validity requirements, and error/result expectations. An agent calling this for a real scene-assignment task would need to infer too much about side effects and parameter meaning.

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 must compensate. It loosely maps 'diffuse bitmap texture loaded from disk' to diffuse_bitmap and 'given objects' to handles, but material_name is entirely unexplained — its default 'MCP_Material' and semantics (unique vs. reused named material) are undocumented in both schema and description. The coverage is only partial.

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 names a specific verb+resource ('Create a Standard material... and assign it to the given objects') and qualifies the variant ('optionally with a diffuse bitmap texture loaded from disk'). It is distinct from siblings like create_object (geometry) and set_property (generic properties); an agent can tell this is material-specific without opening the schema.

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?

There is no statement of when to use this tool versus alternatives such as set_property or run_maxscript, nor any exclusions (e.g., only for Standard materials, or not for physically-based materials). Usage context is only implied by the name and field names, leaving the agent to infer the right invocation scenario.

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