yupao_remove_preset

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

The description says the tool removes a preset and only affects the local machine, but the annotations declare destructiveHint=false. Since removing a saved preset is a deletion of local persisted data, this directly contradicts the non-destructive annotation.

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 front-loaded sentence with no wasted text. It is appropriately terse for a simple one-parameter tool, though the terseness contributes to missing behavioral 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?

For a mutation tool with one undocumented parameter and no output schema, the description should clarify success/failure behavior and deletion semantics. It states the local-only scope, but the destructiveHint contradiction and missing parameter semantics leave important 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?

There is one required parameter, name, with 0% schema description coverage. The description implies that the parameter identifies the preset to remove, but it does not clarify matching behavior, exactness, or what happens if the name does not exist.

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 and resource: removing a specified local search preset. It also scopes the action to the local machine rather than the platform, which helps distinguish it from platform-side operations, though it does not explicitly name sibling preset tools.

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?

Usage is implied by the verb 'remove' plus the local-preset scope, but the description does not say when to use this versus save_preset, search_preset, or list_presets, nor does it state prerequisites or exclusions.

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