get_chat_messages

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

Annotations already provide readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds behavioral details like pagination (limit, offset), sorting (ASC/DESC), and timestamp filters (after/before), which are not in annotations. No contradiction.

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 concise, with a clear purpose statement followed by parameter explanations. It is front-loaded and structured. Minor redundancy could be trimmed, but overall efficient for 6 parameters.

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?

With an output schema present and annotations covering safety, the description sufficiently covers all parameter semantics, filtering, and pagination. No gaps remain for a read-only retrieval tool with this complexity.

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 coverage is 0%, so the description must fully explain parameters. It does so: chat_guid (required), limit (max messages, default 25), offset (pagination), sort (ASC/DESC, default DESC newest first), after and before (epoch-ms timestamps). This adds significant meaning beyond the schema.

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 states 'Get messages from a specific chat', specifying the verb and resource. It distinguishes itself from siblings like get_recent_messages (which likely returns messages across chats) and search_messages by focusing on a single chat with filtering options.

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 explains parameters and their defaults (e.g., sort defaults to DESC, limit defaults to 25) but does not explicitly guide when to use this tool over siblings like get_recent_messages or search_messages. Usage is implied but lacks explicit when-to-use or when-not-to-use guidance.

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