active_fissures

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

The description uses 'List', indicating a read-only operation, and 'active' implies current data, but it does not disclose behavior such as return format, pagination, or what happens with no matching fissures. With no annotations, the description carries the full burden but provides only minimal 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?

The description is a single concise sentence (13 words), front-loaded with the verb, and every word contributes meaning. No redundancy or filler is present.

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?

The description adequately covers the tool's core purpose and lists most filters, but it omits the platform parameter and does not describe return values. Since the schema covers parameters and no output schema exists, the description is mostly complete for a simple listing tool, though it could be slightly more thorough.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description repeats some filters (tier, Steel Path, Void Storm, mission type) but omits 'platform' and adds no syntactic or behavioral details beyond what the schema already provides.

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 it lists active Void Fissure missions, with a specific verb ('List') and resource ('active Void Fissure missions'). It also mentions key filters, distinguishing it from sibling tools that focus on other content like Baro Ki'Teer or mods.

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 implies usage for listing active fissures but provides no explicit when-to-use or alternative guidance. It does not mention when not to use this tool or compare it with siblings like 'world_state', which could also provide mission data, so the guidance is only implied.

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