delete_attribute

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the deletion action but omits any details about irreversibility, side effects, or behavior when the attribute does not exist. For a destructive mutation tool, this is insufficient transparency.

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, front-loaded sentence with no redundant words. It conveys the purpose efficiently and is appropriately sized for the tool's simplicity.

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?

The tool is simple, has only two fully documented parameters, and no output schema, so the description covers the essential purpose. It lacks safety caveats or side-effect details, but for a straightforward deletion operation with full schema coverage, it is mostly complete.

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 both parameters (instancePath and attributeName) fully documented in the input schema. The description itself adds no additional parameter context, but the schema already provides the necessary semantics, so the baseline of 3 is appropriate.

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 an attribute from a Roblox instance' uses a specific verb ('Delete') and resource ('attribute from a Roblox instance'), making the tool's function immediately clear. It also distinguishes from sibling tools like set_attribute and get_attribute, which handle different operations on attributes.

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 clearly implies when to use the tool: whenever an attribute needs to be removed from a Roblox instance. It does not explicitly name alternatives or exclusions, but the context is clear enough, and the sibling tool set (e.g., get_attribute, set_attribute) suggests the intended scope without causing confusion.

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