hires_list_company_mail_accounts

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

Since no annotations are provided, the description carries the burden. It implies a read-only operation via 'List' and scopes to the current company, but it does not disclose pagination behavior, response structure, or potential permissions needed. The 'from_account_id' hint gives some insight into the return contents.

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 sentences with no filler. The core purpose is front-loaded, and the use case is stated succinctly. Every word earns its place.

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 simple list tool with fully documented parameters and no output schema, the description provides sufficient context. It explains what is listed and why it is used. The reference to from_account_id implies the response includes that field, covering the key return value. Slightly more detail on defaults or response fields would make it complete, but it is adequate.

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 input schema already provides descriptions for both page and size (100% coverage), so the description adds no additional parameter-specific meaning. Baseline of 3 is appropriate since the schema handles the documentation.

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 action (list), the resource (mail accounts), and scope (all users in current company). It also provides a specific use case ('resolve from_account_id') that distinguishes it from similar sibling tools like hires_list_user_mail_accounts.

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 gives a concrete scenario ('resolve from_account_id before creating scheduled emails') that tells the agent when to use this tool. It does not explicitly exclude alternatives like hires_list_company_id_mail_accounts, but the 'current company' phrasing narrows the context.

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