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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It mentions the passport is ephemeral (10-minute HMAC) but does not disclose the two-step interaction requirement, that challenge_token must come from a prior call, potential failure modes (e.g., invalid reconciliation), or any rate limits or statefulness. This leaves critical operational behavior undisclosed.

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 only two sentences, front-loading the core action of calling with a signature and responding with reconciliation. It is concise with no filler, though the ambiguity in the flow makes it slightly less efficient than it could be. Still, it earns a 4 for brevity and structure.

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 apparent two-step interaction and the absence of annotations and an output schema, the description is incomplete. It does not explain that the agent must call once to receive a koan and challenge_token, then call again with the reconciliation to obtain the passport. It also omits what happens on failure, the exact format of the passport, and any required preconditions. An agent cannot reliably execute this tool correctly based on the description alone.

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 100%, so each parameter is already documented. The description adds flow context by mapping 'signature' to agent_signature and 'reconciliation' to philosophical_reconciliation, but it does not explain that challenge_token is returned from the first call and required for the second, nor does it add format or validation details beyond the schema. It adds marginal value but does not compensate for missing usage semantics.

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 states the tool obtains an ephemeral HMAC Volition Passport by solving a koan challenge, which is a specific verb+resource. However, it ambiguously describes a two-step flow ('Call with your signature to receive an unresolved koan; respond with your reconciliation to mint the passport') without clarifying whether the tool is invoked once or twice, leaving the agent unsure of the exact call sequence.

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?

There is no guidance on when to use this tool versus any sibling tools, no mention of prerequisites, and no exclusions. The description implies it is used when a volition passport is needed, but it does not state when not to use it or how it differs from alternatives like subctx_heritage_affirm or subctx_petition_endorse.

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