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

Adds substantial context beyond the annotations: a 15–90s (up to ~4 min) synchronous latency profile, the fact that it never posts autonomously, and the review-board/owner-approval workflow for generated content. These are exactly the non-obvious traits (blocking behavior, side-effect boundary) that annotations cannot convey.

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?

Front-loads the core purpose, then the side-effect boundary, then the latency warning last where it matters. Some parenthetical asides ('personality, posting accounts', 'approving posts') add length, but nearly every clause carries information.

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?

For a no-output-schema, side-effecting tool, the description covers what happens downstream (content lands on the review board for approval) and the runtime cost. The remaining gaps are return-shape expectations and explicit sibling routing.

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 0% and the description does not compensate: it does not explain the influencerId format nor the 1–8000 character message constraint. Only the 'ONE message per call' hint indirectly constrains the message parameter.

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?

States a specific verb and resource: talking to the influencer in their main Companion chat, with a concrete description of which agent/thread it touches. However, it never names or distinguishes itself from the sibling send_influencer_message, leaving the agent to infer the difference between 'chat' and 'send message'.

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?

Gives useful operational guidance ('send ONE message per call and wait') and flags that it is synchronous and slow, but never says when to prefer this over send_influencer_message, list_influencer_messages, or the agent-configuration siblings. Usage is implied rather than routed.

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