remove_virtual_bones

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

The description discloses a key behavior: omitting `bone_names` removes all virtual bones. However, it does not mention persistence, permissions, or any side effects. With no annotations provided, the agent is left partially informed about the destructive nature of the operation.

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 concise, consisting of a one-sentence summary and a compact Args section. Every line adds value, and there is no unnecessary filler.

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?

For a simple removal tool, the description covers the main facets: purpose, parameter semantics, and a caveat about 'all'. It relies on the output schema for return values and does not address edge cases, but it is largely complete for this scope.

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 adds meaningful semantics to both parameters, clarifying that `asset_path` is an Unreal asset path and `bone_names` are specific bones, with 'omit for all' explaining the default behavior. This is especially valuable given 0% schema coverage.

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 action ('Remove virtual bones') and the target resource ('a skeleton'). It distinguishes this from sibling remove tools by specifying the bone category, making the purpose unambiguous.

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 that this tool is for removing virtual bones, but it does not explicitly discuss alternatives, prerequisites, or when not to use it. No exclusions or alternative tool references are provided.

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