list_email_accounts

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

No annotations provided, so description carries full burden. Discloses that it lists all accounts, is free, and requires a master API key. Does not mention potential side effects, rate limits, or what happens when no accounts exist. Adequate for a simple read tool but could be more comprehensive.

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?

Three concise sentences, front-loaded with purpose, and every sentence provides essential information (what, why, prerequisite). No redundancy or filler.

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 and zero parameters, the description covers the core functionality, use case, and requirements. It implies the return of email_account_id, but could explicitly state that the response includes IDs. Still sufficiently complete for a simple list tool.

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?

Tool has zero parameters, so schema coverage is 100%. According to guidelines, baseline is 4. Description does not need to add param details, and it mentions the key output (email_account_id) indirectly.

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?

Clearly states the tool lists email accounts, specifies the context (Apollo workspace), and explicitly connects it to finding email_account_id for add_contacts_to_sequence. This directly informs the agent of the tool's role and output.

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?

Indicates when to use (to get email_account_id for add_contacts_to_sequence) and mentions a prerequisite (requires a master API key). Does not provide explicit alternatives or when-not-to-use, but the sibling set is large and the purpose is distinct enough.

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