athena_add_hyperedge

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

With no annotations, the description carries the full burden, but it only notes that provenance is included. It does not disclose mutation side effects, required permissions, idempotency, or any failure behavior. The verb 'Add' implies a write operation, but the behavioral detail is minimal.

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, front-loaded sentence that conveys the core action and key distinguishing feature (n-way) without any fluff. It is appropriately sized and every word adds meaning.

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 tool's complexity—4 parameters, a nested attrs object, and no output schema—the description is insufficient. It does not explain the structure of members, allowed relation types, or how provenance is captured, leaving significant gaps for an agent to use the tool correctly.

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 description coverage is 0%, and the description provides no information about the parameters such as relation, members, actor, or attrs. The terms 'typed' and 'n-way' are general but do not explain how to use the schema fields, leaving the agent without guidance for constructing valid calls.

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 function: adding a typed JSPACE hyperedge or n-way semantic relation, with provenance. The verb 'Add' and resource 'hyperedge' are specific, and the mention of 'n-way' distinguishes it from simple edge tools like athena_add_edge.

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 when a multi-way relation is needed, but it does not explicitly state when to use this tool versus alternatives such as athena_add_edge. There is no mention of exclusions or preferred contexts, only the implicit indication from 'n-way semantic relation'.

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