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

Adds meaningful context beyond annotations: requires a master API key, writes to shared AIsa workspace with no per-caller isolation, making records visible and editable by others. No contradiction with annotations; adds shared-state and auth details.

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 sentences with no redundancy; purpose is front-loaded, duplicate warning and alternatives are clear, and the structure is efficient.

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 key operational details: purpose, duplicate handling, auth requirement, shared workspace implications, and the non-saving enrichment alternative. With an output schema present, return-value explanation is unnecessary; the description is complete for an agent to call correctly.

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 covers all parameters with descriptions (100% coverage). The description adds the unique-domain constraint, which enriches the 'domain' parameter semantics, but does not elaborate on other parameters beyond schema.

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 'Create an account — a company saved into this workspace' with a specific verb and resource, and explicitly contrasts with get_apollo_organizations_enrich, distinguishing it from the enrichment alternative.

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?

Provides explicit guidance: search with post_apollo_accounts_search before creating to avoid duplicate domains, and use get_apollo_organizations_enrich to enrich without saving. Clearly states when not to use and the alternative.

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