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

The description adds meaningful behavioral context beyond the annotations: it consumes one call on the key, records an entry, pins the node to its version and integrity hash, and requires an active Bidda subscription. This gives the agent a clear picture of side effects and proof semantics without contradicting the annotations.

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 compact, front-loaded with the main purpose, and every sentence earns its place: it explains the combined operation, the integrity-pinning behavior, when to use it instead of get_node, and the auth requirement. No unnecessary filler is present.

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?

The description covers the core operation, side effects, prerequisites, and usage context, which is strong given the tool's complexity. The only minor gap is that with no output schema, an explicit statement of the return shape would have been slightly more complete, but the description already implies the node is fetched and the entry recorded.

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 100%, and each parameter already has a detailed description, so the baseline is 3. The tool description reinforces the role of run_id and node_id and mentions api_key, but it does not add substantive parameter-level meaning beyond what the schema already provides.

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 a specific composite action: fetch the full vault node and record a verified node_consulted entry in one call. It also distinguishes itself from get_node by explicitly naming the sibling and the condition for choosing this tool, so an agent can tell them apart immediately.

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 explicitly says 'Use this instead of get_node when you are inside a run,' which is a direct when-to-use instruction with a named alternative. It also states the prerequisite of an active Bidda subscription and that recording happens on an open run, giving the agent the conditions needed to invoke it correctly.

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