send_demo_message

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

With no annotations provided, the description properly discloses the critical safety behavior: 'No message is transmitted.' It also clarifies the synthetic nature of the operation, which is important for a tool whose name might imply real sending. This goes beyond the schema.

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 two short sentences, front-loaded with the action and ending with a critical safety caveat. Every word contributes value.

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 simple tool with two fully described parameters, the description is sufficient: it states the action, the synthetic sink, and that nothing is actually transmitted. It lacks an explicit return value, but that is not essential for this type of operation.

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 100% with each parameter having a clear description. The tool description adds no additional parameter-level detail, so the baseline of 3 applies.

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 clearly states the tool records a simulated outbound message in the synthetic sink, using a specific verb and resource. It distinguishes itself from siblings (read_demo_record, write_demo_note) by focusing on sending a demo message.

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?

Usage context is implied by 'simulated' and 'synthetic sink' indicating a demo/testing environment, but there is no explicit guidance on when to use this tool versus alternatives. No exclusions or alternative references are provided.

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