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

No annotations are provided, so the description carries the full behavioral burden. It hints at write-time classification and hash-pinning, but does not disclose side effects, idempotency, failure behavior, or what pinning actually changes.

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 front-loaded sentence with little waste. Minor redundancy exists because 'write-time pinning' and 'at write time' repeat the same timing concept.

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?

For a tool with no annotations, no output schema, and an undescribed parameter, the definition is too sparse. It does not explain what the tool returns, what a pinned span becomes, or what an agent should expect after invocation.

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?

There is one required parameter with 0% schema description coverage. The description mentions 'ONE span', which loosely implies the text is the span, but it provides no format, size, or validation semantics for the `text` parameter.

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?

It names a specific action cluster (pinning, classify, hash-pin) and scope (ONE span), so the general intent is visible. However, 'span' is undefined and the description gives no clue how this differs from siblings like audit, snapshot, or reinject.

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 phrase 'at write time' gives a temporal context, but there is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent must infer the workflow position entirely.

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