serpwatcher_delete_tracked_keyword

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

Annotations are not provided, so the description carries the full burden. It only states the action and does not disclose whether the operation is idempotent, how the keyword is identified (e.g., via a keyword ID in the body or query), what happens if the keyword is not found, or any side effects. The schema only requires tracking_id, making the invocation unclear.

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 sentence with no filler: 'Remove a keyword from a SERPWatcher tracking.' It is concise, front-loaded, and every word earns its place.

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?

Given this is a delete operation with no annotations and no output schema, the description is too terse. It leaves critical invocation details ambiguous, such as how the specific keyword is identified, what parameters beyond tracking_id are needed, and what response to expect. The tool may be confused with serpwatcher_delete_tracking without more context.

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 the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides. It does not clarify how the body/query parameters should be used to specify the keyword being removed, nor does it explain the distinction between tracking_id and the keyword identifier.

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 'Remove a keyword from a SERPWatcher tracking' clearly states the verb (remove), the resource (keyword), and the context (SERPWatcher tracking). It distinguishes this tool from siblings like serpwatcher_delete_tracking, which removes an entire tracking, and serpwatcher_add_tracked_keyword, which adds a keyword.

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 name and description: use this when you need to remove a keyword from a tracking. However, there is no explicit guidance on when to use it vs alternatives, such as serpwatcher_delete_tracking for deleting the entire tracking, nor are any exclusions or prerequisites mentioned.

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