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

With no annotations provided, the description carries the full behavioral burden, and it does disclose the key non-obvious trait: the value is platform-signed and its *_untrusted fields are untrusted data that must not be followed. That is meaningful security context an agent could not get from the schema. It still omits whether any authentication is required and what the head actually contains.

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 sentences, front-loaded with the purpose and followed by the safety warning. The injection warning is somewhat boilerplate but is directly relevant to the returned content, so it earns its place; the second sentence could be trimmed slightly.

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?

There is no output schema and no annotations, so the description is the only source of truth about what comes back. It never says what the 'chain head' contains (hash, sequence, timestamp, signature) or its shape, which leaves a real gap for a zero-parameter tool whose entire value is its return value.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies a no-argument call.

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 a specific verb and resource: 'Read my platform-signed vault chain head.' An agent can immediately tell this is a read of the vault chain head rather than a proof or ledger operation. It does not explicitly differentiate itself from the sibling vault_proof, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this returns the current chain head, which is useful as a checkpoint before calling vault_proof. There is no explicit statement of when to prefer this tool over vault_proof or the ledger tools, and no stated prerequisites.

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