discord_send

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core action (send/reply) but does not mention potential side effects, permission requirements, rate limits, or failure behaviors. For a write operation, this lack of extra context is insufficient.

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 sentences, front-loaded with the primary action and includes the optional feature. Every word earns its place with no redundancy or filler.

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 send tool with no output schema, the description covers the essential purpose and optional parameter. It could mention return values (e.g., message ID) or channel requirements, but overall it is complete enough for an agent to select and invoke the tool correctly.

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 the description must add meaning to parameters. It does this effectively: 'specified Discord text channel' clarifies channelId, 'message' maps directly, and 'optionally reply to another message by providing its message ID' explains replyToMessageId. It does not detail formats or constraints but adequately compensates for the empty 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 clearly states the action ('Sends a message') and the resource ('specified Discord text channel'), distinguishing it from sibling tools like discord_send_webhook_message. It also mentions the optional reply feature, making the purpose specific and unambiguous.

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 use for sending messages to a text channel and optionally replying, but it does not provide explicit guidance on when to choose this tool over alternatives (e.g., webhook vs. bot message) or mention prerequisites like permissions. No exclusions or alternatives are stated.

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