webex_get_people

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

With no annotations, the description carries the full disclosure burden and falls short: it does not state that this is a read-only directory lookup, what permissions/org scope are needed to enumerate people, or how results are paged (the presence of a 'max' cap of 100 implies pagination that is never explained).

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 front-loaded sentence with no filler, which is appropriate for a simple lookup tool. The trailing 'one required' is terse to the point of ambiguity and slightly undercuts the otherwise clean structure.

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 four-parameter directory search with no annotations and no output schema, the description should explain result shape (list vs. single), pagination/limit behavior, and the relationship to webex_get_person. None of that is present, leaving the agent to infer the key behaviors.

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 75%, so the baseline is 3; the description maps its three named keys to the id/email/displayName properties and adds a selectivity constraint. That constraint ('one required') conflicts with the schema, which declares no required parameters, and it says nothing about 'max' or the 85-ID comma-separated batch syntax.

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 gives a specific verb ('Find') and resource ('org people') plus the three lookup keys (email, name prefix, ID), so an agent knows what it retrieves. It does not, however, distinguish this batch lookup from the sibling webex_get_person (singular), which is the most likely point of confusion.

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?

There is no when-to-use guidance: nothing says this is the directory-search tool to use when the person ID is unknown, and nothing routes the agent to webex_get_person for a known single ID. The only hint is the constraint fragment 'one required', which is not framed as usage advice.

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