delete_profile

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals two meaningful behaviors: the force requirement for profiles outside your own, and the leftover flagged .info for cloud-synced profiles. It does not mention irreversibility, permission errors, or what happens on success, which would strengthen 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?

A single sentence delivers the core purpose and two important behavioral caveats without filler. The information is front-loaded and every clause adds value.

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 description covers the deletion action and the force rule, but it omits semantics for two required parameters, has no output schema, and lacks any note about confirmation or reversibility. For a destructive tool with no annotations, this is a meaningful gap in what an agent needs to call it correctly across scenarios.

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 explains when force=True matters, but leaves the required `type` and `name` parameters undocumented. An agent would not know what values are valid for `type` or how `name` should be formatted.

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 clear action ('Delete') and resource ('profile'), with additional nuance about force and cloud-synced profiles. It does not explicitly contrast with sibling tools, but no sibling is a delete operation, so the core purpose is unambiguous.

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 force condition ('deleting outside your own profiles needs force=True') gives useful context for a specific scenario, and the overall use case is implied. However, it does not explicitly state when not to use this tool or point to alternatives such as rename_profile or create_profile.

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