concur_search_attendees

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds genuinely useful context: the returned fields, the SYSEMP employee type code, tenant-specific behavior, and a security warning that results are third-party untrusted data (prompt-injection guidance). It omits result caps/pagination, keeping it from a 5.

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?

Three front-loaded sentences: purpose, return shape, then usage/security. Efficient overall, though the return-field enumeration could be trimmed since the view enum already covers it.

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?

No output schema, but the description enumerates the returned fields and the untrusted-data caveat, which is what an agent needs to consume results safely. The absence of any result-count/limit guidance is a minor gap for a search tool.

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%, so the schema already fully documents query, view, includeInactive and attendeeTypeKeys. The description adds only the SYSEMP type-code hint; the baseline 3 applies since the schema does the heavy lifting.

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 (search) and resource (Concur attendee directory of colleagues and saved business guests), plus the search key (name or email text). It also distinguishes itself from concur_set_attendees, which is the mutating sibling an agent might otherwise confuse it with.

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?

Explicitly directs the agent to use it to resolve a name/email before calling concur_set_attendees, giving clear context and a named alternative. It stops short of stating when not to use it (e.g., when searching trip travelers or report users), so not quite a 5.

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