000 Init · Kernel Session

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

Annotations provide idempotentHint and destructiveHint. The description adds context: binds actor/floors/audit, mints session_id and authority band, and describes anonymous mode without session. Good additional insight.

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 dense with jargon but front-loaded with core purpose. Could be more concise; multiple concepts packed into a single paragraph.

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 26 undocumented parameters and no formal output schema, the description lists return fields but lacks explanations for most parameters. Incomplete for a complex initialization tool.

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 has 26 parameters with 0% description coverage. The description only lists some modes but misses two enum values (opt_out, opt_out_profiling) and does not explain other parameters like nonce, intent, context, etc. Insufficient compensation.

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 that this tool initiates a kernel session, binds actor, floors, and audit, and is required before other arif_* verbs. It distinguishes from siblings by noting when to use arif_triage or arif_observe instead.

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?

Explicitly states when to use (before other arif_* verbs, if no session) and when not to use (live session bound → arif_triage; pure facts only → arif_observe). Provides clear alternatives.

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