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

Annotations already declare read-only, idempotent, non-destructive; the description adds credential-dependent behavior ('your own position when the credential you are holding is enrolled'), states that reading is free at L0 with no credential, and explicitly says no member data is read. This is meaningful context beyond the hint flags.

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 first sentence states the core purpose and the following sentences cover use cases, return values, auth, and registration route without fluff. It is slightly ornamental, but all content earns its place.

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?

With no output schema and no parameters, the description carries the full load; it covers return values, when to call, and access requirements. It even names the exact sequence to mint a credential, so an agent has everything needed to decide and invoke.

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 has zero parameters and the schema already fully documents that. The description reinforces this with 'Takes no parameters,' so the baseline of 4 applies; there is no additional semantic burden.

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 uses a specific verb ('Read') and names a specific resource (~alter's Golden Thread registration programme), then states exactly what it returns: count woven so far, milestone ladder, and own position when credentialed. That scope separates it from sibling status tools like alter_whoami or alter_presence_read by noting it reads no member data.

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?

It explicitly says to use it before joining to see counts and benefits, or afterwards to check one's position. It also routes agents that want to participate to register_autonomous_challenge then register_autonomous, which clarifies when this read tool is not the right choice.

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