chat_schedule_message

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only says 'schedule a message', which implies a future action, but it does not disclose important traits such as permission requirements, limitations on scheduling (e.g., maximum delay), behavior if post_at is in the past, or whether the scheduled message can be edited or returns an ID.

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 a single sentence, which is concise but lacks substance. It meets the minimum viable length but fails to provide enough context for an agent to understand the tool's purpose or usage effectively.

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 tool has 11 parameters and multiple sibling tools for scheduling (e.g., chat_delete_scheduled_message, chat_scheduled_messages_list), the description is too brief. It does not explain what the tool returns (though an output schema exists), nor does it provide context about message scheduling workflows or constraints.

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?

The input schema has 100% description coverage for all 11 parameters, so the baseline is 3. The description adds no additional semantic meaning beyond the schema; it does not explain parameter relationships or usage patterns.

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 'schedule' and the resource 'a message to be sent to a channel'. It implies delayed delivery, distinguishing from immediate posting tools like chat_post_message, but does not explicitly differentiate from siblings such as chat_delete_scheduled_message or chat_scheduled_messages_list.

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. For instance, it does not mention that this tool is for scheduling and not for immediate sending, nor does it reference related tools like chat_delete_scheduled_message for cancellation or chat_scheduled_messages_list for viewing scheduled messages.

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