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

The description is rich in behavioral detail: decay lifts within ~30s, no review/operator is needed, identity comes from the token, and the return value is the refreshed liveness standing. However, these state-changing self-heal effects directly contradict the annotation `readOnlyHint: true`, so the behavioral profile is unreliable and scores 1 due to annotation contradiction.

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?

Every sentence carries distinct, load-bearing information: purpose, implicit attestation, self-heal trigger, operator-freeze exception, identity handling, return value, and invocation example. There is no filler or repetition of schema details.

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?

Despite zero parameters and no output schema, the description fully equips the agent: it explains what the tool does, when to use it, when not to use it, side effects, delay, identity source, return value, and example invocation. The only significant concern is the annotation contradiction already scored under behavioral transparency.

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 input schema is empty, but the description adds the necessary invocation guidance by giving the example `call federation_attest with arguments {}` and noting that identity is read from the token rather than from parameters. This tells the agent exactly how to invoke the tool correctly.

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 clear verb and object: 'Attest your manager root is alive' and anchors it to the CO 264 liveness mandate. It also distinguishes this tool from freeze/unfreeze/suspend siblings by scoping it to liveness attestation and self-healing only.

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 gives explicit when-to-use guidance: call when idle, or when self-healing a mandate-decayed root. It also gives a clear when-not-to-use situation by stating that an explicit operator freeze is NOT lifted by attesting, and notes that regular privileged activity already counts as implicit attestation.

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