hub_broadcast_event

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

Annotations are absent, so the description carries the full burden of behavioral disclosure. It only says 'track', which implies recording but does not indicate whether it is asynchronous, what side effects occur on each platform, whether failures are tolerated, or what happens to the data after tracking. No return value or response format is mentioned.

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?

A single sentence with no redundant words, well-formed and grammatically correct. It is concise but not misleadingly so; however, the brevity sacrifices necessary detail. It is not front-loaded with key information beyond the core action and scope.

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 tool with no annotations, no output schema, and four parameters with zero schema descriptions, the description is severely inadequate. It does not explain parameter formats, return values, edge cases, or prerequisites. An agent has almost no guidance for constructing a correct call.

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%, meaning the schema provides no explanations for the four parameters (event_name, contact_id, revenue, properties). The description does not compensate—it mentions 'an event' but does not map that to event_name, nor does it explain contact_id, revenue, or properties. This is a critical 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?

States a specific action 'track an event' with a clear scope: 'across ALL connected marketing platforms simultaneously.' This distinguishes it from siblings like track_ugc (UGC-specific), track_signal (signal-specific), and hub_send_campaign (sending campaigns). The meaning is clear, though it could be more explicit about the type of event (e.g., conversion, page view).

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 guidance on when to use this tool versus alternative tracking tools such as track_signal, collect_signals, or track_ugc. It does not mention prerequisites, scenarios, or exclusions. An agent has no reason to prefer this over other tracking tools beyond the vague 'ALL connected marketing platforms' scope.

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