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

Annotations already indicate a write operation (readOnlyHint=false) and destructive potential (destructiveHint=true). The description adds valuable context: it does not connect to telephony systems, and writes are shared across the AIsa workspace with no per-caller isolation. This goes beyond annotation basics and helps agents understand side effects and scope. No contradiction with annotations.

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, front-loaded with the primary purpose. Each sentence carries distinct value: purpose, non-telephony clarification, and workspace sharing behavior. No filler or redundant content.

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 12 parameters all documented, an output schema present, and annotations covering safety, the description covers the key behavioral aspects (shared workspace, non-telephony). It doesn't mention prerequisites, required fields, or error scenarios, but with zero required parameters and schema coverage, this is acceptable. The description is complete enough for an agent to understand how to invoke and what to expect.

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 all 12 parameters are already documented with descriptions. The description does not add extra semantic detail about parameters, such as required relationships (e.g., that contact_id is central) or formats. It relies on the schema, which is adequate, but provides no additional value beyond the baseline.

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 tool logs a call record against a contact, distinguishing it from placing calls or telephony actions. It explicitly says it writes history into Apollo, making the purpose unambiguous and distinct from sibling read/search tools like get_apollo_phone_calls_search or update tools like put_apollo_phone_calls_id.

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 provides context (this is for logging, not placing calls) but does not explicitly name alternative tools or conditions for when to use them. It implies usage but doesn't give clear when-to-use vs when-not-to-use guidance beyond the telephony caveat. No mention of alternative write tools or when to prefer this over other record-creation endpoints.

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