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

Annotations already cover the safe-read profile (readOnlyHint=true, destructiveHint=false), yet the description adds real context: it defines TAM membership semantics, discloses null behavior for connections without a TAM, and explains the {"kind": "tam"} filter leaf with its member/core flags. 'Reading it changes nothing' reinforces rather than contradicts the 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?

The purpose is front-loaded and the prose is dense but coherent; however, the middle sentence about how a run is scoped via the {"kind": "tam"} filter leaf is tangential to invoking this tool and inflates the length. Tightening would help.

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?

There is no output schema, so the description must convey the return shape. It communicates the semantic content (account/contact counts, ICP counts, null case) but never names the response fields, leaving the agent to infer the actual payload structure.

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?

With 100% schema description coverage and a single parameter, the schema already carries connection_id semantics including the list_crm_connections prerequisite. The description adds nothing about the parameter, so the baseline 3 applies.

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 names the precise resource (the connection's TAM) and enumerates its components: an account-level filter, a persona-level filter over contacts, and an ICP layer with counts. That is far more specific than a name restatement, but it never explicitly states the retrieval verb and does not differentiate itself from the sibling get_tam_outward.

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?

No sentence says when to call this versus alternatives such as get_tam_outward or set_tam, and no prerequisite beyond the schema's own 'Call list_crm_connections first' is given. The null case ('Null when the connection has no TAM') is a return-value note, not usage guidance.

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