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

Annotations already declare readOnlyHint=true and destructiveHint=false Mendelsso. The description adds that it returns mail accounts for all users in the current company, which is useful scope beyond the title. However, it does not mention pagination behavior, response shape, or ordering despite page/size parameters existing.

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?

One tight sentence that front-loads the action and resource, then adds a purpose clause. No fluff, no repetition of the tool name or title. Excellent clarity per word.

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 description covers the main use case (resolving from_account_id for messages) and the scope ('all users in the current company'). However, with no output schema and only pagination params, the absence of any note about max page size, defaults, or response fields leaves some ambiguity for an agent planning an exact call.

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 0% and the description adds no parameter guidance. 'page' and 'size' are conventional, but the tool text does not explain defaults, limits, or how they interact with the 'all users' scope, leaving the agent to guess at expected values.

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 uses a specific verb-resource pair: 'List mail accounts of all users in the current company'. This clearly distinguishes it from siblings like hires_list_user_mail_accounts and hires_list_company_id_mail_accounts by specifying scope (current company, all users) without needing to open either schema.

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 phrase 'use to resolve from_account_id for messages' gives a concrete use case for selection. It doesn't explicitly name alternatives or exclusion criteria, but the disclosed scope ('all users in the current company') lets an agent infer when this tool is the appropriate choice versus user-specific or company-ID-specific listers.

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