chat_send

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

It discloses streaming behavior via MCP logging notifications, the final answer in the result, and the ability to abort with the 'signal' parameter. No annotations present, so description bears full burden and satisfies it well.

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 sentences front-load the purpose, add behavioral details, and provide usage for abort. No superfluous content.

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?

Covers streaming behavior and abort, but omits explanation of two boolean parameters and their defaults. No output schema, so description lacks return details beyond 'final answer'.

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 0%, so description must explain parameters. It only mentions 'signal' (abort) and implicitly 'message' but does not explain 'sessionId', 'webSearch', or 'enableThinking'.

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 verb 'Send a message' and the resource 'open Sakana chat session'. It distinguishes from sibling tools like 'chat_interrupt' by focusing on sending messages.

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 description implies the session must be open and explicitly mentions using signal:'abort' to interrupt. However, it does not compare with sibling tools like 'chat_interrupt' or provide when-not-to-use guidance.

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