set_pose_search_schema_role

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds value beyond them by disclosing the collision-based refusal path and the returned fields (including 'saved', implying persistence to disk). That is useful mutation context not present in the annotations.

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 tightly written sentences plus a return-value line; the core rename action and its failure condition are front-loaded. The parenthetical 'default role when omitted' slightly duplicates the schema but costs little.

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, the description supplies the return shape and the refusal behavior, which an agent needs to interpret results. Combined with full schema coverage and mutation annotations, this is nearly complete; only a note on required permissions/persistence timing is absent.

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 all three parameters are already documented, including the 'empty = default role' semantics for role_from. The description largely restates that, adding only the FName framing. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (rename) and a precise resource (the role/FName of the schema's FPoseSearchRoledSkeleton entry), including the default-target behavior. This clearly separates it from siblings like add_pose_search_roled_skeleton and remove_pose_search_roled_skeleton.

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?

Explains the selection context (omit role_from to target the default role) and a precondition for failure ('Refused when new_role is already taken by another entry'). It does not name alternative tools for other rename scenarios, but the when/why is clear.

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