Delete an instance

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

No annotations provided, but description fully discloses: recursive deletion, enforced write pipeline with auto rollback on failure, and restrictions on deletable objects. All behavioral traits beyond schema are covered.

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?

Three concise sentences, each critical. First states core purpose, second details behavioral contract, third adds usage constraint and aid. No redundant words.

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?

Single parameter, no output schema. Description fully addresses all necessary information: scope of deletion, procedural behavior, restrictions, and prerequisite step for obtaining input.

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 coverage is 100% with description for 'guid'. Description adds value by instructing to use studio_browse to acquire guid, which is helpful for agent.

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?

Describes specific action: delete instance including children (subtree). Distinguishes from siblings by stating it's deletion, not adding/browsing. Explicitly lists excluded objects (services). References how to obtain guid via sibling tool.

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 explicit when-not-to-use: cannot delete service singletons. Implies context for deletion with force and rollback. Does not explicitly list alternatives but guidance is clear.

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