delete_profile

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the destructive action ('Delete') but does not mention irreversibility, whether the deletion is permanent, any cascading effects, or what happens to dependent data. The minimal wording fails to add context beyond the word 'Delete'.

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 a single, short sentence that directly states the action and target. There is no filler or redundant phrasing, making it highly efficient and easy to parse.

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 tool with one parameter and no output schema, the description is adequate but leaves gaps. It does not clarify whether the deletion is reversible, if there are any prerequisites (e.g., profile must exist), or what the return value looks like. Given the low complexity, a slightly more detailed description would be expected, so a 3 is appropriate.

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 coverage is 100% because the only parameter 'profile_id' has a clear description: 'UUID of the profile to delete'. The tool description also mentions 'by UUID', which reinforces but does not add additional meaning beyond the schema. Baseline 3 applies when schema covers all parameters.

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 uses a specific verb ('Delete') and resource ('profile from the machine's internal storage'), and mentions the key identifier ('by UUID'). It clearly distinguishes from sibling tools like 'update_profile' or 'get_profile', which perform different actions on the same resource.

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 usage when the intent is to remove a profile, but it does not explicitly state when to prefer this tool over alternatives or mention any exclusion conditions. The context is clear but lacks direct guidance on alternatives, which keeps it at a mid-level score.

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