teams_read_chat_messages

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

With no annotations, the description carries the full burden. It does disclose a behavioral trait the schema cannot: results are returned 'oldest first' and cover only the 'most recent' messages. However, it says nothing about authentication/account requirements, pagination, rate limits, or what happens when the chat is empty, and the truncated tail may have contained more.

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?

Front-loaded with purpose, then ordering, then the source of the identifier — a sensible information order with no filler. Evaluation is limited by the visible truncation, but what is present is tight.

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 no-parameter, no-output-schema, no-annotation read tool, the description covers scope, ordering, and identifier provenance. It is missing the volume/limit behavior and any account or permission context, and the cut-off tail leaves it unclear whether those were stated.

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 input schema declares zero properties, so the baseline is 4 and there are no parameters for the description to explain. It does add provenance for the implied chat_id ('from teams_list_chats'), which is more than the empty schema offers — though the mismatch between a referenced chat_id and an empty schema is a small inconsistency worth noting.

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?

States a specific verb and resource: 'Reads the most recent messages of a Microsoft Teams chat.' The scope ('most recent') and ordering ('oldest first') distinguish it from teams_read_channel_messages and teams_search_messages, though it never names those siblings explicitly. The sentence is truncated, so the full scope statement (likely a message limit) is not visible.

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?

It gives one useful routing hint — chat_id comes from teams_list_chats — which tells the agent how to obtain the prerequisite identifier. There is no statement of when to prefer this over teams_read_channel_messages or teams_search_messages, and no exclusions or preconditions beyond that single pointer.

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