add_material_function_output

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only lists parameter descriptions and defaults, without mentioning side effects, permissions, persistence, or recompilation triggers. Essential behavioral context is missing.

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 a single clear sentence plus a structured Args list. It is front-loaded with the purpose, and every line adds value. No unnecessary text.

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?

The description covers all parameters and purpose, and an output schema exists for return values. However, it lacks usage context and behavioral transparency, leaving gaps for someone unfamiliar with the tool's role among siblings.

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?

Since schema description coverage is 0%, the description compensates well by detailing each parameter: function_path gets 'Full path', output_name gets an example list, and sort_priority explains display order. This adds substantial meaning beyond the schema's type/default information.

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 'Add an output pin to a Material Function,' which is a clear verb+resource combination. It effectively communicates the tool's primary function, but does not explicitly differentiate from siblings like add_material_function_input.

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 over alternatives. With numerous sibling tools for material functions (e.g., add_material_function_input, set_material_function_output), it fails to mention the specific context or prerequisites for use.

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