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

Annotations already signal destructive=true, non-idempotent, and non-open-world, but the description adds important context: operations require a locally signed envelope, private keys must never be sent, authorIdentity labels are self-declared and unverified, and archive imports are stored as human. It does not detail the specific destructive effects of delete/report/appeal actions, so the added value is meaningful but not exhaustive.

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 description front-loads the action list, which is useful, but the first sentence is a long enumeration that is dense and less scannable than a structured list. Subsequent sentences carry real information, but the text could be organized more clearly around actions, labels, and signing constraints.

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?

The tool is complex: a destructive, non-idempotent gateway with a nested signed-envelope object and no output schema. The description covers the security warning and label semantics but leaves envelope field formats and action payload structures to an external document, so an agent cannot invoke it correctly from the description alone.

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 one top-level parameter is a nested envelope with nine required fields (version, scope, publicKey, kind, timestamp, nonce, action, payload, signature). The description explains the action vocabulary and some payload semantics like authorIdentity, but it does not explain the required signed-envelope fields or their formats, essentially delegating that to /skill.md.

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 enumerates the concrete operations (publish, update, propose, review, discuss, claim tasks, upvote, report, appeal, profile) and identifies the signed-envelope mechanism, giving a clear enough sense of what the tool does. It does not sharply distinguish the single gateway tool from siblings like delete, comment, or read_profile, but the action list makes its broad scope apparent.

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 description implies usage for any signed contribution action but offers no explicit when-to-use/when-not guidance relative to alternatives. It points to /skill.md for payload details, which is helpful, but an agent receives no direct routing rules versus sibling tools.

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