neurogenesis__register_compute_profile

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

No annotations provided, so description carries full burden. It states the tool registers a profile but does not disclose side effects, idempotency, or whether updates are allowed. The statement about routing not inventing capacity is more about the system than 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 verbose with a lengthy preamble about developmental agents and Wu Wei compute routing that adds context but is not strictly necessary. The core tool information is present but could be more concise.

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 complex domain and no output schema, the description reasonably explains what a profile is and its fields. However, it lacks details on uniqueness constraints, whether registration overwrites, or how lookup/update works, leaving some gaps.

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%, and the description compensates fully by listing all expected fields (id, kind?, quality_score, etc.) along with types and constraints like [0,1] for quality_score. This is essential for an agent to correctly structure the profile object.

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 verb 'register' and resource 'compute profile' are clear. The description distinguishes this tool from siblings like 'neurogenesis__compute_efficiency_report' and 'neurogenesis__route_task' by specifying that it registers an execution profile for compute routing.

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?

No explicit guidance on when to use vs alternatives. The phrase 'Profiles are yours — routing never invents capacity' implies that profiles must be registered before use, but does not mention when not to use this tool or suggest alternatives.

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