Manage Saved Searches

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotency, so the safety profile is covered. The description adds real context beyond that: 'delete removes one for good' flags irreversibility, and 'Nothing is sent to any employer and nothing is spent' bounds side effects. It does not describe alert delivery behavior or timing, keeping it just short of a 5.

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?

A single dense paragraph that front-loads what the resource is, then walks the actions in order, then handles routing and safety. Every clause carries new information with no 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?

With an output schema present, return values need not be described, and the description covers action semantics, the prerequisite that saved_search_id comes from action list, and the destructive nature of delete. An agent has everything needed to call it correctly.

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 all four parameters (name, action, alerts_enabled, saved_search_id) are already documented in the schema, including the default naming behavior when save receives no name. The description restates the action semantics and which params apply to which action but adds no syntax or format detail 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?

The description states a specific verb and resource ('Manage the user's saved searches: named snapshots of their job preferences') and enumerates each action's effect. It distinguishes itself from siblings by explicitly naming aiapplyd_update_job_preferences as the tool for changing match preferences and pointing to aiapplyd_get_matches as the next step.

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?

It gives per-action when-to-use guidance ('action "list" shows them', 'call it only when the user asks' for delete) plus an explicit exclusion and the alternative to use instead ('Do not use it to change what the user is matched with; use aiapplyd_update_job_preferences'). Nothing is left to inference.

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