get_recent_flow_activity

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavioral context: exactly one API request, variable time span based on network busyness, and FIREWALLA_BOX_ID scoping with fallback to every box. There is no contradiction with annotations.

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 three well-organized sentences: definition, use/don't-use guidance, and scope. Every sentence earns its place, and the core purpose is front-loaded.

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 no output schema and no parameters, the description adequately covers return content, limits, request behavior, and scope. An agent has all the information needed to select and invoke this tool accurately.

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?

There are zero parameters, so there is no parameter burden on the description. It still adds relevant invocation context by explaining the implicit FIREWALLA_BOX_ID environment scoping, which is directly useful for calling the tool correctly.

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: 'Get a snapshot of the 50 most recent network flows (one GET /v2/flows request)'. It names the output dimensions (protocol, region, blocked/allowed counts), and its contrast with search_flows distinguishes it from the closest sibling.

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 explicitly says when to use the tool ('what's happening right now?', current security threats, immediate network issues) and when not to use it (historical analysis, >50 flows, daily/weekly patterns), pointing to search_flows with a concrete query example 'ts:>24h'.

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