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

Beyond the destructiveHint annotation, the description discloses key behavioral consequences: deletion is permanent, cannot be undone, and any HTML fetching the readUrl will receive a 404. It also states the authentication requirement. These are concrete operational details that materially affect how an agent should invoke and reason about the tool.

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?

Four short sentences, each adding distinct value: the core action, the downstream 404 effect, irreversibility, and the group/personal/auth usage rule. The most important fact is front-loaded, and there is no filler or repetition of the schema.

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 operation with a full input schema, output schema, and annotations, the description supplies all essential behavioral context: permanence, side effect on readUrl, auth requirement, and the group-vs-personal selection logic. An agent has enough information to invoke the tool correctly and understand the consequences.

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?

The schema already covers all four parameters with descriptions at 100% coverage, so the baseline is 3. The description repeats the group_id semantics but does not add meaningful parameter details beyond what the schema already states. No additional syntax, format, or relationship guidance is provided.

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 opens with a specific verb and resource: 'Permanently deletes a data slot.' It clearly differentiates from sibling tools like set_data_slot, get_data_slot, list_data_slots, and other delete_* tools by immediately identifying the target resource and the destructive nature of the operation.

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 provides clear usage context: group slots require group_id, personal slots omit it, and authentication is required. It does not explicitly name alternatives or exclusion conditions, but the group-vs-personal distinction and auth prerequisite give an agent enough situational guidance.

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