delete_profile

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

With no annotations provided, the description carries full responsibility and does so thoroughly. It explicitly flags the operation as destructive, explains the default preview path, states the confirmation requirement, and names the exact deletion targets: the profiles.db row and the ~/.universal-db-mcp/<name>/ subdirectory.

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 compact and front-loaded with the core action, followed by a warning and essential safety details. Every clause carries useful information; there is no redundant 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 covers the critical aspects: destructive nature, preview behavior, confirmation flag, and exact delete scope. It does not state what happens after a confirmed deletion or how errors are surfaced, but for a profile deletion tool the key behavioral contract is well specified.

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 50%, with only confirm documented. The description adds meaning for name by implying it selects the target profile, and for confirm by specifying the actual side effects of deletion and the preview result. This goes beyond the schema's terse '二次确认' description.

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?

Description opens with '删除指定 profile', a specific verb and resource that exactly identifies the tool's function. It is clearly distinguishable from sibling profile tools like create_profile, update_profile, and get_profile, as well as from delete_template.

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 conveys clear context: this tool deletes a profile and requires confirm=true for actual deletion. However, it provides no explicit guidance about when to prefer this tool over alternatives or when not to use it, leaving usage selection mostly implied.

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