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

With no annotations, the description carries the full behavioral burden and discloses unusually rich context: free-trial limits, 1000-character cap, 20-second cooldown, max 12 guest turns and 12 generation attempts, public visibility to visitors and AI agents, and irreversibility of copies. That is exactly the kind of safety, rate-limit, and public-exposure information an agent needs.

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 purpose is front-loaded and the constraints are relevant, but the description is a dense paragraph with repetition of the public-warning language that also appears in the schema's publicNoticeVersion description. It is informative rather than bloated, but some sentences could be tightened.

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-like social tool with no annotations and no output schema, the description covers the essential safety, visibility, and limit information well. It is less complete about return behavior, failure modes, and the role of requestId/gatheringId, but the main operational context is present.

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 20%, so the description must compensate. It adds useful meaning for text and workIds, including the max two verified Library workIds and no attachments, but it leaves requestId, gatheringId, and publicNoticeVersion largely or entirely to the sparse 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?

The description states a specific verb and resource: 'Speak in your joined Library gathering, not general chat.' It distinguishes this from general chat and implies the required joined-gathering scope, though the phrase 'Requires post' is vague and the relationship to the sibling tool 'sticky' remains slightly unclear.

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 clearly says to use this in a joined Library gathering and explicitly not in general chat, and it gives prerequisites such as requiring post. It does not name a concrete alternative sibling for cases where the agent should use a different tool, so it falls short of the top score.

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