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

The description discloses important behavioral traits beyond the annotations: statefulness ('the SAME persistent thread and memory'), side effects on future posting, synchronous latency (15–90s, up to 4 min), and the restriction that it cannot publish. These traits are not inferable from the annotations alone. 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?

The description is dense but efficiently organized: purpose, statefulness, constraints, latency, and the alternative tool are each covered in a few sentences. No filler or repetition; the most decision-relevant information is front-loaded.

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?

Despite having no output schema, the description provides enough context for correct invocation: it explains behavior, latency, one-call-at-a-time semantics, the inability to publish, and the sibling alternative. An agent can confidently decide whether to call this tool and how to handle the response.

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 description coverage is 0%, so the description carries the burden of explaining parameters, but it only implies that 'message' is a single conversational turn and does not explain influencerId or message semantics beyond field names. The names are somewhat self-explanatory, but this is still a clear gap.

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 uses a specific verb and resource: 'have a live conversation with the influencer's agent brain.' It clearly distinguishes this tool from siblings by emphasizing the persistent thread/memory shared with the dashboard Chat tab and the advice-only, no-publishing constraint.

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 explicitly says when to use this tool (live, synchronous conversation) and when not to ('For fire-and-forget direction, prefer send_influencer_message'). It also gives concrete usage guidance: send ONE message per call and wait for the slow reply.

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