Init Session

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

Annotations already indicate idempotentHint=true and no destructive/read-only flags. The description adds behavioral context: it is a 'governed constitutional session' and provides timing info for modes. No contradictions. Could mention more about side effects or requirements.

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?

Two concise sentences, front-loaded with the critical instruction to call first. No wasted words; efficiently communicates the core usage and mode options.

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 (25 parameters, governance-related, multiple modes), the description is insufficient. It omits parameter semantics and does not explain how to use the various mode values or other fields. The output schema exists but does not compensate for missing input guidance.

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%. The description does not explain any of the 25 parameters (e.g., mode, actor_id, ack_irreversible). The agent must rely solely on the schema, which lacks descriptions. This is a major gap for such a complex input schema.

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 purpose: 'Start or resume a governed constitutional session.' It emphasizes calling it first before any other tool, distinguishing it from all sibling tools by being a prerequisite.

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 explicit ordering guidance: 'Call this FIRST before any other tool in a new conversation.' It also explains mode options ('init' vs 'light') with time estimates, helping the agent decide. However, it does not detail when not to use or explore alternatives.

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