delete_assistant

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 tool deletes an assistant and returns JSON, but does not disclose whether deletion is permanent, what happens to related tasks or memory, required permissions, or any other behavioral trait beyond the tool name itself.

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 short and front-loads the purpose. The Args section is clear. The 'Returns: JSON result' line is somewhat redundant because an output schema exists, but it does not significantly detract from an otherwise efficient structure.

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 delete operation with no annotations and an output schema, the description is incomplete. It fails to warn about irreversibility, permissions, or side effects, leaving the agent without enough context to invoke the tool safely. The output schema covers return values, but behavioral context is missing.

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 does provide a minimal label for the single parameter ('assistant_id: Assistant id to delete'), which is enough to identify it, but adds no format, source, or lookup guidance. This meets the minimum for a simple ID parameter but does not go beyond it.

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 states a specific verb and resource: 'Delete an assistant profile.' This distinguishes it from sibling deletion tools like delete_provider and delete_memory, though it does not explicitly differentiate it from adjacent assistant tools such as update_assistant or disable_assistant.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention prerequisites, warnings about irreversibility, or the relationship to enable_assistant/disable_assistant. Usage is only implied by the verb 'delete'.

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