wavefunction__register_collective

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

No annotations are provided, so the description carries full burden. It states 'register' implying a write operation, but does not disclose idempotency, duplicate handling, auth requirements, rate limits, or side effects. This is insufficient for an agent to understand the tool's behavior.

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 that front-loads the tool category and action. However, the structure is somewhat cramped with the colon and list; it could be more readable with bullet points or clearer separation.

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?

With 6 parameters, no output schema, and no annotations, the description is too sparse. It does not explain return values, error conditions, or validation rules. For a registration tool, this is inadequate for an AI agent to use it reliably.

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%, so the description must compensate. It mentions some parameters (mission, domain profile, constitutional scores, capacity) but omits two required parameters (collective_id, name). The description adds partial meaning but misses key details.

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 explicitly states the action ('Register') and the resource ('agent/collective into the match index'), and lists key fields (mission, domain profile, constitutional alignment scores, capacity). It clearly distinguishes from sibling tools like wavefunction__find_matches or wavefunction__intake.

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 provides context ('demand-side agent/collective discovery') but does not give explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it. No exclusions or comparisons to siblings are provided.

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