rename_static_mesh_socket

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

Annotations already declare idempotentHint=true and destructiveHint=true, so the description repeating 'idempotent' adds little. However, 'guards against name collisions' is genuine behavioral context not present in the annotations, and with no output schema the explicit return fields add useful disclosure. It still doesn't say what happens when a collision is hit (error vs. auto-rename).

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?

Two compact lines with zero filler. The purpose is front-loaded and the return shape follows, so an agent gets the essential information immediately.

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?

With no output schema, including the return fields is a meaningful addition, and the mutation/collision behavior is flagged. The remaining gap is the collision outcome and whether an explicit save is required, which the 'saved' return field hints at but never explains.

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 100%, so the schema already documents static_mesh_path, socket_name, and new_name. The description adds no syntax, format, or constraint detail beyond what the schema provides, making the baseline 3 appropriate.

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 precise verb+resource: 'Rename an existing static mesh socket'. The resource specificity ('static mesh socket') cleanly separates it from siblings like rename_skeletal_mesh_socket, add_static_mesh_socket, and remove_static_mesh_socket without opening any 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?

The word 'existing' implies a precondition (the socket must already be present), but there is no explicit when-to-use guidance and no mention of alternatives such as add_static_mesh_socket for creating or remove_static_mesh_socket for deleting. Usage is only implied.

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