selector_hint_delete

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

With no annotations, the description carries the full burden and does so well: it discloses irreversibility ('This cannot be undone'), the failure mode (key/domain mismatch), and the preferred follow-up path. It stops short of describing any file-location or permission prerequisites, so it is strong but not exhaustive.

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?

Three short sentences, each earning its place: action, reason/irreversibility, alternative, and error condition. The destructive nature is front-loaded in the first word.

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 two-parameter destructive tool with no annotations and no output schema, the description covers the essentials an agent needs: irreversibility, the failure precondition, and the replacement workflow. It omits only secondary details such as where the hints file lives or what auth is required.

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 100%, so both 'key' and 'domain' are already documented in the schema. The description only implies the domain-key pairing through the failure condition and adds no format or default details beyond the schema; baseline 3 is appropriate.

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?

States a specific verb ('Permanently remove') and resource ('a saved selector hint from the hints file'), and its scope is immediately distinguishable from the sibling selector_hint_save/get/list operations without opening any schema.

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?

Gives an explicit trigger scenario ('when the site changed and the selector no longer works') and routes the agent to the correct alternative ('save a corrected hint with selector_hint_save'). It also documents the when-not condition ('Fails if no hint with that key exists for the domain').

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