Get Last Outgoing Messages

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

With no annotations, the description carries the full transparency burden. It discloses the data scope and that delivery status is included, but it does not state read-only behavior, result ordering, pagination/limits, or whether the returned structure contains anything beyond the messages and their statuses.

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 one compact sentence that front-loads the main resource (outgoing messages) and then adds the two relevant modifiers: all chats and the time window with delivery status. There is no filler or unnecessary repetition.

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?

The core selection criteria are present, but because there is no output schema and no annotations, the description leaves out practical invocation details such as result ordering, maximum result count, and the exact fields returned for each message. It is adequate for basic selection but not fully complete.

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 schema only describes `minutes` as an integer with a default of 1440, while the description adds the key semantic that it is the trailing window length for the query. This meaningfully clarifies how to use the parameter, though it could also note bounds or an effective maximum.

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 identifies the resource as outgoing messages across all chats, scoped to the last `minutes` minutes and including delivery status. The qualifier 'Исходящие' (outgoing) distinguishes it from the sibling get_last_incoming_messages, and the tool name supplies the 'get' verb.

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?

The intended usage is implied: call this when an agent needs recent outgoing messages with delivery status across all chats. However, it does not explicitly state when not to use it or which sibling to prefer for incoming messages, per-chat history, or other filtered queries.

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