foundry_send_chat_message

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

With only readOnlyHint=false in annotations, the description carries the burden of explaining behavior, but it merely says 'create', which does not clarify whether the message is sent immediately, requires permissions, or affects the game log. No additional behavioral context is given.

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 is very short, but it is under-specified rather than concise. A single vague sentence fails to provide necessary detail, making it not appropriately sized for a tool with 8 parameters.

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?

Given the complexity (8 parameters, no output schema, mutation behavior), the description is completely inadequate. It does not mention return values, side effects, or any operational context needed for correct invocation.

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 25% (only userId and clientId have descriptions), and the tool description adds no explanation for parameters such as content, speaker, whisper, or chatType. The description does not compensate for the low schema coverage at all.

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 'Create a chat message' names a verb and a resource but uses 'create' instead of 'send', which is vague and does not distinguish from the sibling tool foundry_send_chat_as_user. It lacks specifics about the chat context or how this differs from other chat-related tools.

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?

No guidance is provided on when to use this tool versus alternatives like foundry_send_chat_as_user or foundry_list_chat_messages. There are no usage scenarios, constraints, or exclusions.

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