deleteIKChains

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

No annotations are provided, so the description carries full burden. It states the action is deletion, implying destructive behavior, but doesn't disclose critical details like whether deletions are permanent, require specific permissions, have side effects on related resources, or provide confirmation prompts. For a destructive tool with zero annotation coverage, this is a significant gap.

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, efficient sentence with zero waste—'Delete multiple IKChains' is front-loaded and directly conveys the core purpose without unnecessary words. Every word earns its place.

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 destructive tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., irreversibility, error handling), usage guidelines, and output expectations. Given the complexity of deletion operations and minimal structured data, more detail is needed to adequately inform an AI agent.

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%, with the 'ids' parameter documented as 'IKChain identifiers to delete'. The description adds no additional meaning beyond this, as it doesn't specify format, constraints, or examples for the IDs. Baseline score of 3 is appropriate since 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?

The description 'Delete multiple IKChains' clearly states the action (delete) and resource (IKChains), with 'multiple' indicating batch operation. It distinguishes from sibling tools like 'deleteJoints' or 'deleteConstraints' by specifying IKChains, but doesn't explicitly differentiate from similar delete operations beyond the resource type.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing IKChains to exist), when not to use it, or how it compares to other deletion tools like 'deleteIKChains' versus individual deletions. Usage is implied by the name alone.

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