find_users

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

No annotations provided, so description carries full burden. It mentions search fields, parameters like onlyRegistered and includeDisabled, and scanLimit for performance, but does not explicitly state read-only nature, rate limits, or query behavior for empty strings.

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?

Two paragraphs: first states purpose and usage, second adds parameter hints and return fields. Front-loaded and no unnecessary sentences. Every sentence adds value.

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?

Covers search fields, return fields, and parameter usage. With 5 params and no output schema, it is fairly complete. Could improve by describing search matching behavior (e.g., partial match, case sensitivity).

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 100%, baseline 3. Description adds value with parameter guidance: 'Set onlyRegistered=true' and 'Increase scanLimit on larger systems.' It also provides query examples, enhancing understanding.

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 the tool searches across extension number, name, email, and mobile, with examples. It specifies 'Use this when the user asks about people, extensions, or phone users,' distinguishing it from sibling tools like find_contact_by_phone.

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 provides explicit usage context ('when the user asks about people...') and a specific condition ('Set onlyRegistered=true for who is online/registered?'). It lacks explicit exclusions or alternative tool references.

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