atlas_anomaly_bursts

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

No annotations provided, so description bears full burden. Describes detection behavior but does not disclose output format, data freshness, or any constraints. Adequate for a simple read-only tool, but could add more behavioral context.

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?

Single sentence, front-loaded with key concept 'Multi-country coordinated anomaly bursts'. Efficient and to the point, no wasted words.

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?

Tool is simple (no params, no output schema). Description covers basic purpose but lacks details on what constitutes an anomaly, time window, or return value. Adequate but could be more complete for a self-contained tool.

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?

No parameters in input schema (0 params), so baseline is 4. Description does not need to add parameter information; it is self-explanatory for a parameterless tool.

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?

Clearly states the tool detects multi-country coordinated anomaly bursts, with specific verb 'detects' and resource 'anomaly bursts'. Distinguishes from siblings by focusing on coordinated campaigns across countries.

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?

Implies usage for detecting coordinated censorship events, but no explicit when-to-use, when-not-to-use, or alternatives. Context from description suggests scope but lacks guidance on sibling tools like anomaly_dbscan or atlas_timeline.

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