slack_list_scheduled_messages

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

The description only notes the routing path ('/api/tools/invoke') but does not disclose any behavioral traits such as authentication requirements, data scope, pagination, or side effects. With no annotations, the description carries the full burden, and it largely fails to provide useful transparency.

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 very short but lacks substance; it is not front-loaded with critical information. Each sentence is low-value and does not earn its place, making it under-specified rather than appropriately concise.

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?

Despite having an output schema, the description omits the fundamental purpose and behavior of the tool. For a tool with low complexity, it is completely inadequate, leaving an agent with no actionable understanding.

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 sole parameter 'arguments' is described as a 'JSON string of arguments for the connector operation' but no details on expected keys or format. With 0% schema description coverage, the description should compensate but only adds minimal generic context.

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 merely repeats the tool name ('Slack connector operation `list_scheduled_messages`') without stating what it does. It does not clarify that it retrieves a list of scheduled messages in Slack, leaving the purpose ambiguous. This is essentially a tautology of the name.

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 (e.g., slack_delete_scheduled_message, slack_search_messages). There is no mention of context, prerequisites, or scenarios where this tool is appropriate or not.

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