find_confluence_users

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states that the tool searches and returns user details, but never mentions pagination behavior, how multiple criteria interact, whether at least one parameter is required, authorization needs, or what happens on empty results. This is a significant gap for a search tool with seven optional parameters.

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 compact at two sentences and front-loads the core purpose immediately. However, the final bolded sentence 'Use this tool when you need to find users based on a query' is largely redundant with the first sentence, making it not entirely waste-free.

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 seven optional parameters and no output schema or annotations, yet the description gives no guidance on parameter relationships (e.g., can cql be combined with username?), which search criterion to prefer, or what the response structure looks like. This leaves the agent under-informed for a flexible 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?

The schema has 100% description coverage, so the baseline is 3. The description adds no parameter-specific semantics beyond the general phrase 'based on various criteria,' which does not meaningfully extend what the schema already documents for cql, username, accountId, etc.

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 opens with a specific verb and resource: 'Searches for Confluence users based on various criteria.' It further clarifies scope by stating it's for 'finding user details like account IDs' when you have 'partial information or need to perform a broader search,' which distinguishes it from direct lookup tools like get_confluence_user.

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 explicitly says 'Use this tool when you need to find users based on a query' and adds context about partial information and broader searches. However, it does not explicitly name sibling tools like get_confluence_user or list_pages_created_by_user, nor does it state when NOT to use this tool.

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