hub_send_transactional

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'send a transactional message' but does not explain side effects, error conditions, authentication requirements, or what 'best platform' entails. It does not disclose whether this is a read-only or mutating action, nor any rate limits or performance characteristics.

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 a single sentence, which is concise, but it lacks structure and front-loading of critical information. It fails to prioritize key details like the single-contact constraint or the channel parameter. The vagueness of 'best platform' makes the sentence low in information density, so the conciseness is not beneficial.

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 5 parameters, no output schema, and no annotations, the description must provide substantial context. It covers almost nothing: no mention of required fields, channel options, deep linking, or the meaning of 'best platform'. An agent would be unable to confidently invoke this tool correctly based on the description alone.

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 must compensate for undocumented parameters. It provides zero information about contact_id, body, title, channel, or deep_link. The agent cannot infer the meaning of these parameters from the description alone, making parameter usage entirely dependent on the schema (which itself lacks semantic details for non-enum params).

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 states a specific action ('Send a transactional message') and scope ('single contact'), which distinguishes it from sibling tools like hub_send_campaign or hub_broadcast_event. However, the phrase 'via the best platform for the channel' is vague and fails to clarify what 'best platform' means or how it is determined, leaving ambiguity about the tool's exact behavior.

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 gives no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or conditions that would steer an agent to a sibling tool like hub_send_campaign or hub_broadcast_event. The only implicit differentiator is 'single contact', but that is not explicit.

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