webex_get_messages

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing beyond the bare operation. It does not state that this is a read-only operation, whether pagination is required or capped for large spaces, or that includeFileDetails triggers one HEAD request per file (cost information living only in the schema).

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?

A single sentence with zero filler, and the primary mode (single message) is front-loaded ahead of the listing mode. Nothing redundant is included.

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 7-parameter tool with no annotations and no output schema, the description covers the core intent but omits pagination behavior, the exclusivity of messageId vs roomId, and what a listing returns. The schema picks up most parameter detail, leaving it merely adequate.

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 86%, so the schema already explains each parameter and the baseline is 3. The description adds only the pairing of messageId with single lookup and roomId with listing, without clarifying mutual exclusivity or how before/beforeMessage interact with listing.

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?

Names a specific verb ('Get') and resource ('message'/'space messages') and discloses the two operating modes keyed to messageId vs roomId. It does not name a sibling such as webex_search_messages, so the differentiation from search is left to inference.

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 'or' construction implies the two modes: supply messageId for a single lookup, roomId for a listing. There is no explicit when-not guidance, no pointer to webex_search_messages for content-based lookup, and no note on how pagination parameters interplay with listing.

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