admin-delete-user-preference

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states the action 'delete' without explaining consequences such as irreversibility, idempotency, or error behavior if the key does not exist.

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 concise sentence, front-loading the action and scope without unnecessary 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?

For a simple delete tool with two required parameters and no output schema, the description covers the core operation and parameter meanings. However, it lacks details on return values or error conditions, which are important for agents invoking the tool blindly. Given no annotations, this leaves some gaps.

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 description explains that the operation deletes by 'key' for a 'specific user,' mapping directly to the required parameters key and user_id. Although schema description coverage is 0%, the description effectively clarifies the role of each parameter, even though it doesn't explicitly name them.

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 states 'Admin: delete a preference by key for a specific user,' clearly identifying the verb (delete), resource (preference), and scope (key + user). This distinguishes it from siblings like admin-delete-all-user-preferences.

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 'Admin:' prefix indicates this is an administrative action, and the phrase 'by key for a specific user' implies it's for deleting a single preference. However, it does not explicitly mention alternatives or exclusions, such as 'for bulk deletion use admin-delete-all-user-preferences.'

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