List messages in a Saved sub-dialog

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds the filtering behavior by original sender peer, but does not disclose pagination behavior, return format, or other behavioral details beyond annotations.

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 concise sentence that is front-loaded with the key action and resource. No wasted words or redundant information.

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?

For a simple read-only pagination tool, the description is adequate but lacks details about return format and pagination behavior. Since there is no output schema and only a basic description, the agent may not know what fields the fetched messages contain or how pagination parameters interact.

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 only 25% (only 'peer' has a description). The description clarifies that 'peer' means 'original sender peer', but limit, offsetId, and accountId are left unexplained. With low schema coverage, the description does not adequately compensate for the missing parameter semantics.

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?

Description states 'Fetch messages inside one Saved-Messages sub-dialog' with a specific verb and resource, and clearly differentiates from siblings like get_saved_dialogs and search_saved_messages by specifying the sub-dialog scope and filtering by original sender peer.

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 description implies when to use the tool (for fetching messages from a specific saved sub-dialog), but it does not explicitly mention alternatives or give exclusions. No 'use X instead' guidance is provided.

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