map_object_delete

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

Annotations already mark destructiveHint=true, and the description adds the key behavioral detail that deletion requires explicit confirmation via 'confirm=true'. This is beyond what annotations provide, though full side-effects (e.g., cascade deletion) are omitted.

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?

A single, front-loaded sentence with no extraneous words. Every word earns its place, conveying purpose and a crucial usage requirement efficiently.

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?

Given destructiveHint annotations and an output schema (not shown), the description is minimally adequate. However, it omits prerequisites (e.g., object existence) and fails to explain the object_id parameter, leaving gaps for an agent to infer correctly.

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 0%, so the description must compensate. It only mentions 'confirm' but does not explain 'object_id'—a required parameter with ambiguous type (string or integer). The agent lacks guidance on what value to use for the identifier.

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 verb 'Delete' and the resource 'live scene object', making the tool's function immediately obvious. It distinguishes from sibling tools like map_object_create and map_object_update by specifying deletion.

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 explicitly requires 'confirm=true', which is a critical usage condition. While it doesn't list alternatives or when-not-to-use scenarios, the sibling tool names provide natural context for when to use delete vs other operations.

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