trigger_patrol

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool 'extracts scenes' and 'generates memory nodes,' implying it creates or modifies persistent state, but it does not clarify if this is a read-only operation, what side effects occur (e.g., deletion of previous markers), or any rate limits or authorization beyond the env var.

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 one concise sentence plus a single prerequisite statement. Every word earns its place; no filler or redundant information.

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?

While the description clarifies the tool's core function and a key prerequisite, it lacks details about the output (no output schema provided) and the exact nature of 'memory nodes' or 'scenes.' For a tool with only two parameters and no complex return value, the description is adequate but could be more complete by mentioning what the tool returns.

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 documents both parameters with descriptions (100% coverage), so the description adds minimal value beyond mentioning the LLM_API_KEY requirement. The parameter semantics are adequately clear from the schema alone.

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?

Description clearly states the tool's action: 'Run patrol — extract scenes from conversation and generate memory nodes.' It uses a specific verb ('run') and resource ('patrol'), and the resulting extraction and generation distinguish it from sibling tools like 'search_memory' or 'conclude_topic'.

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?

The description mentions the prerequisite 'Requires LLM_API_KEY env var,' providing some guidance on when the tool is usable. However, it does not specify when to use this tool versus alternatives like 'recall_memory' or 'search_history,' nor does it give any 'when-not' to use it.

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