unity_gameobject_delete

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

Discloses key behavior: refusal on shared mesh, reports 'sharedWith', and force override. Without annotations, this adequately covers behavioral traits, though it omits details on reversibility or side effects.

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 sentences with no wasted words. Front-loads primary purpose, then adds a crucial behavioral note. Highly concise and structured.

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?

Covers unique behavior (shared mesh) for a moderate-complexity tool with 4 params and no output schema. Lacks details on consequences like undo, but sufficient for common use.

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 covers all parameters (100% coverage). Description adds context about force parameter's role in overriding shared-mesh refusal, going beyond the schema's basic 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?

Clearly states 'delete a GameObject by path or name', specifying the verb and resource. Distinguishes from siblings as the only deletion tool among many Unity tools.

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?

Provides condition for when tool refuses (shared mesh), but does not explicitly state when to use versus alternatives like disabling or other operations. Lacks explicit when-not-to-use guidance.

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