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

Annotations already declare a non-read-only, non-idempotent, closed-world write, so the safety profile is known. The description adds that the envelope is stamped with a mark and anchored to a shared trust root, which hints at a dependency on prior mark setup, but it never says whether repeated calls mint new attestations, what must pre-exist, or what the envelope 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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes partly from omitting needed detail rather than from tight editing.

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 mutation tool taking an untyped nested object, this is under-specified: no event structure, no trust-root prerequisites, no note on non-idempotent re-issuance. The output schema means return values need not be described, which keeps the score off the floor.

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?

Schema description coverage is 0% and the sole parameter is a free-form nested object with additionalProperties=true and no field documentation. The description never mentions the "event" argument or its expected shape, so nothing compensates for the schema gap.

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 names a verb ("Issue") and a resource ("agent-attestation envelope"), so the general action is inferable. However, the modifiers "mark-stamped" and "under the shared trust root" are undefined jargon, and nothing distinguishes this from the sibling viridis_certify_envelope or viridis_certify, which plausibly do overlapping envelope work.

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?

No guidance on when this tool should be chosen over viridis_certify, viridis_certify_envelope, or viridis_verify_mark. There are no stated prerequisites (a registered mark, a trust-root identity) and no exclusions, so the agent must guess from the name alone.

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