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

No annotations are provided, so the description carries the full disclosure burden. It does add one genuinely useful behavioral fact – that the verifier is not run at call time – implying a deterministic read of a committed artifact, plus 'self-notarized' implying authenticity. It stops short of stating read-only semantics, failure modes, or what happens when no witness is committed.

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?

It is a single tightly-packed sentence, which is appropriately sized, but the front-loaded clause is the least parseable part and burdens the reader with jargon before delivering the actionable detail (Binance BTCUSDT, no verifier execution). Efficient in length, weak in readability.

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?

An output schema exists, so return values need no explanation, and there are no parameters to document. The remaining gap is that a zero-input, cryptically named tool among equally cryptic siblings gives the agent almost no basis for deciding whether to call it – the fundamental purpose/usage context is missing.

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. Schema coverage is moot at 0 params, and the description introduces no parameter confusion.

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 leans on dense, undefined jargon ('projection of a committed Shōgen-verified witness') and never states plainly what the tool returns or accomplishes. 'Binance BTCUSDT, self-notarized' narrows the domain but does not resolve the core verb+resource. It offers no differentiation from the cryptic siblings calibrate, cascade, and gate.

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 explicit when-to-use guidance and no comparison against the sibling tools. The clause 'the verifier is NOT executed at call time' hints that this is a read of already-committed data rather than a trigger for verification, but that is inference, not instruction. The agent is left to guess the scenario in which attest is the right choice.

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