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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the safety profile is covered. The description adds genuinely new behavioral context: the message is the sole visibility channel for players, HTML is passed through, and actorId changes how the post is attributed and rendered. It doesn't say what comes back (a message reference) for follow-up edits.

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?

Purpose is front-loaded in the first clause and the reminder about player visibility lands early. The single dense paragraph packs in a lot of useful detail, though the trailing document-link syntax is a run-on fragment rather than cleanly structured text.

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?

With no output schema and a mutation annotation set, this covers the essentials an agent needs: what to send, how it renders, who sees it, and how to link documents. The only real gap is return-value information, which matters because follow-up edit/delete calls need the new message's ID.

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 100%, so a 3 is the floor, but the description earns more: it supplies the @UUID[Type.id]{Label} link syntax that appears nowhere in the schema, and gives concrete examples for flavor ("Narration", "The Tavern") plus the portrait behavior of actorId. The speaker/actorId precedence is left to the schema, which already covers it.

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 ("Send a message to the Foundry chat log") and enumerates the content types it carries. It does not name the sibling boundary against chat-update or chat-list, so an agent must infer that this is the create path and the others are read/edit paths.

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 list of use cases (narration, NPC dialogue, combat descriptions, OOC) implies when to reach for it, and the note that players only see what is posted here hints at why. But there is no explicit exclusion or pointer to chat-update for editing an existing message, which is the most likely confusion among siblings.

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