get-user-by-email

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

No annotations are provided, so the description carries the full burden. It states 'Returns single user with complete details' but does not disclose behavior for missing emails, rate limits, authentication needs, or any side effects. For a read-only lookup, this is minimal.

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?

Single sentence with emoji, clear and to the point. Every word adds value, and the structure is front-loaded with purpose.

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?

Given no output schema, the description adequately explains the tool's function and result (single user with complete details). Could optionally mention edge cases (e.g., if email not found), but overall sufficient for the 3 parameters and sibling context.

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%, so baseline is 3. The description adds no additional meaning beyond the schema's descriptions, which already explain the parameters (email, client_gravatar, include_custom_profile_fields). No extra depth provided.

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 'EXACT LOOKUP: Find a user when you have their exact email address.' It specifies the verb (find), resource (user), and condition (exact email), and distinguishes from siblings like 'get-user' and 'search-users' by emphasizing exact match.

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 says 'Use this when you know the specific email and need detailed profile information,' implying when to use, but does not explicitly state when not to use or mention alternatives. Siblings include 'get-user' (for other identifiers) and 'search-users' (for partial matching), but no exclusions are given.

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