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

With no annotations provided, the description carries full behavioral disclosure. It reveals that the tool changes status and triggers all enabled hunters, and it names the reverse operation. It does not cover edge cases like already-active searches or partial hunter failures, but the core side effect is clearly stated.

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?

Two short sentences deliver the core behavior and reversibility with no filler. The action is front-loaded, and the reference to sdr_pause_search is relevant and compact.

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 one-parameter mutation tool, the description covers the essential behavior and reversibility, but it omits parameter semantics and any mention of expected output or preconditions. It is adequate for a straightforward activation, yet leaves some ambiguity about the id and what happens on repeat calls.

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?

The input schema has one required 'id' string with no description, and schema description coverage is 0%. The description never clarifies that 'id' is the Signal Search identifier or what format it should take, so it adds no meaning beyond the property name itself.

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 concrete action: 'Set status=active and fire-start all enabled hunters,' identifying both the resource (a Signal Search) and the scope. It is clearly distinct from sibling tools like sdr_pause_search and sdr_run_now because it names the activation side effect explicitly.

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?

No explicit guidance is given for when to use this tool versus sdr_resume_search or sdr_run_now, both of which are plausible alternatives in the sibling list. The only indirect hint is 'Reversible via sdr_pause_search,' which tells the agent how to undo but not when this tool is the correct choice.

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