remove_profile

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 reveals an important behavior (switching away from the active profile before removal) but does not mention that removal is permanent or irreversible, or any potential side effects or error conditions. This is adequate but not comprehensive.

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 two short, front-loaded sentences. The first sentence states the primary action clearly, and the second adds a critical behavioral nuance. There is no redundant or extraneous information.

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 simple destructive tool with no annotations or output schema, the description covers the core purpose and the active-profile edge case. However, it lacks details about permanence, error handling, or prerequisites (e.g., listing profiles first), making it minimally complete but not fully thorough.

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 input schema has one required parameter 'name' with no description (0% coverage). The tool description does not explain the parameter beyond the obvious 'profile name', and does not clarify where to obtain valid values or any format constraints. This leaves the parameter's meaning largely implicit.

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 tool removes a profile, using the specific verb 'Remove' and identifying the resource ('a profile'). It also adds a distinguishing behavioral note about handling the active profile, which sets it apart from sibling profile management tools.

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 implies when to use this tool (to delete a profile) but does not explicitly mention alternatives or exclusions. The added note about OBS switching away from the active profile provides context on edge-case handling, which is useful for decision-making.

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