threat_rules__evaluate_event

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

With no annotations, the description carries the full burden and does not disclose that this is a read/analysis operation, whether any rule can block or mutate anything, or what the response contains. Most critically, it is silent on the 'lane' values enforce/alert/hunt, where 'enforce' clearly implies consequence-bearing behavior that an agent must understand before calling.

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?

It is a single front-loaded sentence with no padding, which is good, but it is so short that it reads as truncated (trailing '…') rather than deliberate. Brevity here comes at the cost of needed detail rather than from efficient editing.

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 3-parameter tool with no annotations, no output schema, and two undocumented enum parameters, the description is far too thin. An agent cannot tell the return format, the effect of lane selection, or when to prefer this over the sibling evaluate_* tools.

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 coverage is only 33%: 'lane' and 'format' have no descriptions, and the description adds nothing about either despite both being enums with meaningful choices. The parenthetical (type, content, fields, sessionId, …) merely restates what the 'event' parameter's schema description already says, so no new semantic value is added.

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 names a specific verb ('Evaluate') and a specific resource ('structured ATR AgentEvent JSON'), and even sketches the payload shape. It is clear what the tool acts on, but it never says what 'evaluate' means in practice (which rule set runs, what the verdict looks like) and gives no hint of how it differs from the sibling threat_rules__evaluate_text / evaluate_file.

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?

There is no indication of when to pick this over threat_rules__evaluate_text, threat_rules__evaluate_file, or threat_rules__list_rules. The only implicit cue is that the input is an AgentEvent object, which the caller must infer rather than being told explicitly.

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