get_material_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It lists the categories of returned information (Principled inputs, textures, render settings, users), which adds some value, but it does not state whether the operation is read-only, what happens on an unknown material name, or error behavior.

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 compact sentence that is efficiently front-loaded with the purpose and scope. It earns its space without fluff, though the brevity also reflects the lack of deeper guidance.

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 tool with one parameter and no output schema, the description is too thin. It omits usage context, parameter explanation, and behavioral caveats, and provides no differentiation from a large set of similar sibling tools. An agent would struggle to call it correctly.

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 for the single 'name' parameter. It never explains what 'name' refers to (material name? object name?) or its expected format, leaving the agent to guess at the parameter's meaning.

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 states a clear verb+resource ('get material details') and enumerates what it covers: Principled main inputs, textures, render settings, and users. However, it does not distinguish itself from the many sibling get_* tools (get_object_info, get_camera_info, get_light_info, list_materials), leaving differentiation to the agent's inference.

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 guidance on when to use this tool versus alternatives such as list_materials, get_node_tree, or get_object_info. The description gives no context about whether this is for a single material by name, nor any exclusions or prerequisites.

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