rec_profile_delete

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

The description states a destructive action ('Delete a profile and its checklist file') while the annotations declare destructiveHint=false, directly contradicting the declared safety profile. No other behavioral context (permissions, irreversibility, whether the profile must be stopped first) is given to offset this.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity is partly the cause of the missing usage and parameter detail.

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?

An output schema exists, so return values need not be described, but the description omits essential context for a deletion tool: profile identity semantics, interaction with checklist files, prerequisites, and reverting. Combined with the annotation conflict, it is not sufficient to call the tool safely.

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 single 'name' parameter has 0% schema description coverage, so the description must compensate and does not. It never clarifies that 'name' identifies the profile, how it is matched (exact/case-sensitive), or how it relates to the checklist file being removed.

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 names a specific verb (Delete) and resource (a profile and its checklist file), which is clearer than the bare name. However, it does not distinguish itself from the sibling rec_delete (and from rec_profile_save/list/get/start/stop), leaving the agent to infer that this tool only operates on profiles.

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 when-to-use, when-not-to-use, or alternative guidance. With siblings like rec_delete and rec_profile_save/get/list present, the description should state whether this is the profile-lifecycle delete versus the recording delete, but it offers nothing.

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