find_confluence_users

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

No annotations are provided, so the description must fully disclose behavioral traits. However, it only states what the tool does and does not mention that it is read-only, any permission requirements, rate limits, or side effects. The agent lacks awareness of safety implications.

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 with three sentences: purpose, usefulness context, and a clear instruction. It is front-loaded with the core action. No unnecessary words, though the bold sentence could be integrated.

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 search tool with 7 parameters and no output schema, the description covers purpose and usage scenario but lacks explanation of return format, pagination behavior (though in schema), and whether results are sorted. It is adequate but not fully complete.

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% with all 7 parameters explained. The description does not add new meaning beyond 'various criteria' and the bold directive. Baseline score is appropriate as schema handles 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?

The description clearly states it searches for Confluence users based on various criteria, distinguishing it from sibling get_confluence_user (single user retrieval) and search tools for pages. The verb 'searches' and resource 'Confluence users' are specific, though a bit generic.

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 to use this tool when you need to find users based on a query, especially when you have partial information or need a broader search. It does not explicitly mention alternatives or when not to use, but the context implies that get_confluence_user is for exact lookups.

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