webex_search_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. It discloses that the tool scans history and is not a global search, but it omits permissions, rate limits, pagination behavior, and how scanLimit versus maxResults affect execution.

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 single sentence is front-loaded and free of wasted wording. It is perhaps too terse for the tool's complexity, but structurally it is concise and readable.

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?

The tool has five parameters, no annotations, and no output schema, yet the description is a single sentence that leaves result format, pagination, and execution behavior undocumented. It provides only the space-scoping context and does not fully prepare an agent to invoke the tool correctly.

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 description maps loosely to the required roomId and query parameters, but the schema already documents those fields. It adds no meaning for before, scanLimit, or maxResults, which lack schema descriptions; with 60% schema coverage, the description provides only marginal additional value.

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 states a specific verb ('Keyword search') and resource ('messages' implied by the tool name) within one space, and clarifies scope by contrasting with global search. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as webex_get_messages or webex_search_spaces.

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 phrase 'within one space; scans history, not global search' implies when to use the tool and gives one exclusion, but it does not name alternatives or explain when to prefer webex_get_messages for listing versus this tool for keyword search.

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