chat_scheduled_messages_list

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

Lacking annotations, the description provides minimal behavioral insight. It doesn't mention pagination (cursor), time filtering (latest, oldest), or scope (team_id), which are critical for understanding tool behavior.

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, efficient sentence with no extraneous information. Every word serves a purpose.

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?

While the tool is simple, the description lacks context on pagination, default behavior, and return structure. The output schema exists, but the description could be more complete given the six optional parameters.

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 100%, so all parameters have clear descriptions. The tool description adds no additional semantics beyond the schema, leading to a baseline score.

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 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 explicit guidance on when to use this tool versus alternatives. The sibling tool names imply it's for listing, but no context on filtering or scope is provided beyond what parameters suggest.

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