chat_scheduled_messages_list

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

No annotations are provided, so the description bears full responsibility. It only says 'List scheduled messages' but does not disclose pagination behavior, effect of optional parameters, or that it is a read-only operation (no side effects).

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 extremely concise (three words), but it lacks crucial details for a tool with multiple parameters. It is front-loaded but insufficiently informative.

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 6 parameters and an output schema, the description is incomplete. It doesn't explain how to use filters (channel, time range, pagination) or what the output contains, leaving the AI agent to guess.

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?

Parameters (channel, cursor, latest, limit, oldest, team_id) are entirely undocumented. The description adds no meaning to any parameter despite 6 optional parameters and 0% schema description coverage.

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 'List scheduled messages' clearly states the action (list) and the resource (scheduled messages). It distinguishes from sibling tools like 'chat_schedule_message' and 'chat_delete_scheduled_message'.

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. For instance, it doesn't mention that filtering by channel or pagination parameters are available, nor does it specify that it retrieves all scheduled messages for the authenticated user or a specific channel.

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