superpos_hive_map

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

No annotations provided, so description carries full burden. It mentions 'point-in-time map' and 'timeframe bounds activity-derived edges', implying it is read-only. However, it does not explicitly state non-destructive behavior, required permissions, or how null hive_id is handled.

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: two sentences with no wasted words. It front-loads the core purpose ('point-in-time map of the hive graph for drill-down') and then adds the key detail about timeframe.

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?

Covers main concept (nodes and edges with timeframe filtering) but lacks specifics on output structure (though output schema exists) and behavior for null hive_id. Adequate for a map tool but leaves some questions unanswered.

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 0%, so description must compensate. It explains timeframe with examples ('1h', '24h', '7d'), but does not explain hive_id (anyOf string/null, default null) – leaving ambiguity about what null means. Only one of two parameters gets meaningful context.

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 provides a 'point-in-time map of the hive graph' for drill-down, listing specific node types (agents, services, inboxes, schedules) and edge types (task flow, proxy access, triggers, cross-hive links). This distinguishes it from siblings like superpos_hive_agents (lists agents only) and superpos_list_hives (lists hives).

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 use for drill-down into the hive graph, but does not explicitly state when to use versus alternatives (e.g., superpos_hive_agents for a flat list of agents). No exclusion criteria or prerequisites are mentioned.

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