What ARCANE's public World-Sense serves and what it explicitly does NOT serve, plus per-stream validation notes. ARCANE NOTICES present-state geopolitical risk from primary-source senses; it does not forecast, advise, or trade.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool only serves present-state information and does not forecast, advise, or trade, which is valuable for safe usage. However, it does not mention read-only nature or other potential side effects.
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 extremely concise, consisting of only two sentences. Every sentence provides essential information without redundancy.
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?
Given the absence of parameters, annotations, and output schema, the description covers the tool's purpose and limitations adequately. It could be more complete by describing the format of the returned validation notes, but overall it is sufficient.
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 tool has no parameters, so the description is not required to provide parameter information. A baseline score of 4 is appropriate as there are no additional semantics needed.
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 clearly states the tool's purpose: providing information about what ARCANE's World-Sense serves and does not serve, including per-stream validation notes. It distinguishes itself from siblings by focusing on capabilities and limitations.
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 states what the tool does not do (forecast, advise, trade), providing guidance on when not to use it. However, it does not explicitly name alternative sibling tools for related tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool has a clearly distinct purpose: overview, domain drill-down, system status, deltas, bilateral tracking, scenario tracking, trigger chains, data streams, score composition, and capabilities. No two tools overlap in function.
All tools use the consistent pattern 'arcane_<descriptive_noun>' in snake_case, making it easy to infer purpose from the name.
10 tools is appropriate for a geopolitical risk monitoring system covering overview, detailed breakdowns, data streams, status, and analysis. Each tool earns its place.
The tool surface covers every aspect of the server's stated purpose: current overview, domain drill-down, scenario tracking, trigger chains, bilateral relations, data streams, system status, and score composition. No obvious gaps.