get_material_property_connections

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

With no annotations, the description carries full burden. It states the tool 'lists slots that have something connected,' implying it is a read-only query. However, it does not clarify whether it modifies anything, requires specific permissions, or how it handles disconnected slots beyond not listing them.

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 extremely concise with two sentences, front-loading the main action and clarifying a key constraint. Every word adds value; no filler or unnecessary repetition.

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 is clear in scope but lacks details such as what constitutes an 'expression node' or 'output slot' in the context of Unreal materials. Given the availability of an output schema, the return structure is covered, but the description alone is minimally adequate for understanding the tool's function within the larger material graph toolset.

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?

The description provides no explanation for the 'material_path' parameter, such as its expected format or how it is used (e.g., asset path, object reference). With 0% schema description coverage, the description fails to add any semantic value beyond the schema's minimal definition.

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 uses the verb 'Query' and specifies it lists which expression node feeds each material output slot. It clearly distinguishes from sibling tools like 'trace_material_connection' by focusing specifically on output slot connections and noting it only returns connected slots.

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 implies the tool is for inspecting material connections but provides no explicit guidance on when to use this tool over alternatives (e.g., trace_material_connection, get_available_material_pins) or prerequisites like whether the material must be loaded.

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