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

Annotations already cover safety (readOnly=false, destructive=false, idempotent=true, openWorld=true). The description adds real context beyond them: no account/credential needed and no automatic publication or training consent. However it does not explain the idempotency mechanism (client_id dedup), the approve-gate behavior, or what the operator review actually does to the submission.

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?

Two tight sentences with the core action front-loaded and no padding. Efficient, though the second sentence packs two claims (no credential, no publication/training consent) that would read better separated.

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 20-parameter mutation tool with 15% schema coverage, no output schema, and a required approve-flag, a two-sentence description is far too thin. It omits the meaning of most parameters, the review lifecycle, and what a caller gets back after queuing.

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 only 15% across 20 parameters, so the description is expected to compensate and does not. It touches only the three action types in participation_action ('feedback, appreciation, shared-memory') and vaguely gestures at authorization, leaving fields like expected_version, public_status, source_ids, and approved_to_submit semantics undocumented anywhere.

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?

States a specific verb (queue) and the resources handled (feedback, appreciation, shared-memory action) plus the destination (operator review), which differentiates it from siblings like submit_feedback, appreciate_encounter and save_shared_memory that act directly. The phrase 'exact authorized' is jargon that adds little, and the 'draft/queue vs publish' distinction is only implied.

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 through 'for operator review,' suggesting this is the staged/draft path rather than direct submission, but it never says when to choose it over submit_feedback, appreciate_encounter, or save_shared_memory, nor what preconditions (approved_to_submit, client_id) are required. Usage is inferable but not stated.

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