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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds real context beyond them: the operation is reversible ('create_saved_search with the same filters brings it back'), it 'reaches no one else' (blast radius limited to the caller), and it requires the user's Cotlet API key with app access. This explains the non-destructive framing rather than contradicting it.

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?

Front-loaded with the purpose, but the first two sentences are largely redundant ('Delete one of your saved searches and its notifications' vs 'Deletes one saved search and stops its notifications'). The reversibility and auth notes earn their place, but the duplication is wasted space.

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 single-parameter delete tool with no output schema, the description covers the key concerns an agent needs: scope (only the caller's search), reversibility, and the required credential. Nothing critical is missing, though it could note whether the search must be listed first.

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?

Only one parameter (saved_search_id) with 100% schema coverage, so the schema already documents it ('Saved search ID from list_saved_searches'). The description adds no syntax or sourcing detail beyond what the schema provides, so baseline 3 applies.

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 and resource ('Delete one of your saved searches and its notifications'), naming exactly what is removed. An agent can distinguish it from hemnet_list_saved_searches and hemnet_create_saved_search 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?

Explains it 'runs without asking' (no confirmation needed) and that create_saved_search with the same filters reverses it, giving clear context for when to invoke and how to undo. It stops short of explicitly stating when NOT to use it versus the sibling list/create tools, but the guidance is clear.

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