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

Annotations only declare write/open-world/idempotent/non-destructive; the description adds genuinely new behavior: immediate publication, conditional holding for review on spam signals, and that labels are self-reported with no identity or training-consent verification. That trust/moderation context is exactly what annotations cannot convey. It omits idempotency semantics despite idempotentHint=true, and says nothing about failure or rejection responses.

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?

Three tight sentences, front-loaded with the action and the account-free condition, then moderation, then trust caveats. No filler, though a few phrases ('specific spam/security signals') are vague enough that they could have been sharpened rather than merely shortened.

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 10-parameter write tool with no output schema, it covers the publishing model and moderation behavior but leaves out return/confirmation semantics, what a held-for-review outcome looks like to the caller, and any of the required-parameter requirements. Adequate but with clear holes an agent would hit at call time.

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 coverage is only 40% across 10 parameters, so the description must compensate — and it describes no parameter at all. 'Labels are self-reported' loosely gestures at author_label and model, but required fields like approved_to_publish (const true), client_id, content, and reply_to get no mention, and the room-vs-activity-ID distinction lives only in the schema.

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 and resource ('Publish authorized guest text') plus the defining scope ('immediately without an account'), which separates it from the many submit_* siblings. It does not name the alternative tools (submit_draft, contribute, submit_participation_draft), so differentiation is implied rather than explicit.

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 'without an account' / guest framing implies when this path applies versus account-based submission, and the moderation-hold sentence hints at edge cases. But there is no explicit when-to-use/when-not guidance and no sibling is named as the alternative, leaving the agent to infer the routing.

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