Read the conversation on an item

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 known. The description adds useful details: ordering (newest first) and inclusion of replies. It does not describe pagination, return format, or error behavior, but with annotations covering the read-only nature, this is acceptable.

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, front-loaded sentence. It starts with 'Returns the updates' and immediately conveys the primary action and resource. No wasted words; every phrase adds value (e.g., 'newest first, with their replies' is useful behavioral detail).

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 tool with two well-documented parameters and read-only annotations, the description is adequate. It explains what is returned (updates, replies, ordering) and the title clarifies the use case. It lacks pagination details, but the schema covers the limit parameter. Given the low complexity, this is complete enough.

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% (both limit and item_id have descriptions). The description adds no parameter-specific information beyond what the schema provides. Since the schema already documents defaults and types, the baseline of 3 applies.

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 the tool returns updates, which are the item conversation, newest first, with replies. This is a specific verb+resource ('returns updates') and clarifies the scope (item conversation). However, it does not explicitly distinguish itself from sibling tools like monday_create_update, though the name and context imply the read nature.

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 provides clear context: use this to read the conversation on an item. The title 'Read the conversation on an item' reinforces this. It does not mention exclusions or name alternatives, but the existence of monday_create_update for writing implies the read use case. This is clear context without explicit 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.