delete_hub_profile

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

The description goes beyond the destructiveHint annotation by explicitly warning that the deletion is permanent and removes all associated data. This is clear and accurate.

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, front-loaded with the primary purpose, and includes a practical parameter hint without unnecessary filler.

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 is missing essential context for one required parameter (hub_profile_id), and does not mention any confirmation or result behavior. This leaves the agent underinformed for a destructive action.

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?

Only workspace_id is explained, and its source is given. hub_profile_id is required but not described at all, leaving a significant gap for the agent to infer its meaning and origin.

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 action ('permanently delete a hub profile and all its data') and emphasizes irreversibility, which distinguishes it from reversible alternatives like archive_hub_profile or restore_hub_profile.

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?

It provides limited guidance by telling the agent to get workspace IDs from list_workspaces(), but it does not explicitly explain when to choose deletion over archiving or what conditions should lead to permanent deletion.

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