add_material_function_input

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

No annotations are present, so the description must handle behavioral disclosure entirely. It fails to mention any important traits such as whether adding an input with an existing name overwrites or fails, any permission requirements, or the effect on the material function graph. This is a significant gap for a mutation tool.

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 front-loaded with a clear one-line purpose, followed by a well-organized parameter list. Each parameter has a brief, useful comment. Minor redundancy exists (e.g., repeating 'preview_value' in preview_value's comment), but overall concise.

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 9 parameters, no annotations, and no output schema, the description covers parameter semantics well but omits broader context. Missing information about return behavior, error conditions, and operational context (e.g., graph changes). It's adequate but not fully complete.

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 schema description coverage at 0%, the description provides thorough parameter explanations including types, enums, and usage hints (e.g., 'JSON array for default value'). It adds essential meaning beyond the raw schema, which only lists types and defaults.

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 verb 'Add' and resource 'input pin to a Material Function'. It is specific about the operation but does not differentiate from sibling tools like 'set_material_function_input' or 'add_material_function_output', which perform related but distinct actions.

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 is provided on when to use this tool versus alternatives. For example, it doesn't mention that this tool creates a new input pin while 'set_material_function_input' modifies an existing one. The agent receives no context for appropriate selection.

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