slack_schedule_message

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

No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits: permissions required, side effects, error behavior, or return value. The description merely provides infrastructure routing details.

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 short but wastes space on routing details ('Routes through /api/tools/invoke under your JWT, tenant, and company scope') instead of front-loading the tool's core function. It is underspecified and not efficient.

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 of scheduling a Slack message and the absence of annotations or output schema details, the description is completely inadequate. An agent has no way to understand how to use this tool effectively.

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 one parameter 'arguments' with no description (0% coverage). The description adds only 'JSON string of arguments for the connector operation,' which does not explain what valid arguments are or their structure. No added semantic value beyond the 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 states 'Slack connector operation `schedule_message`' but does not explain what scheduling a message entails. It fails to distinguish from similar tools like `slack_post_message` which sends immediately. The routing details are irrelevant to purpose.

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 on when to use this tool versus alternatives such as `slack_post_message` or `slack_delete_scheduled_message`. No mention of prerequisites, context, or exclusions.

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