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

With no annotations provided, the description carries the full burden, and it does disclose an important behavioral guardrail: the destination is fixed server-side and the tool cannot be used to send to arbitrary addresses. However, it does not describe side effects, required permissions, rate limits, or what happens on success or failure.

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 first sentence is effective and front-loaded, but the second sentence largely restates the first ('never accepts a recipient argument' vs 'The request never accepts a recipient'). The third sentence adds useful security context, but the redundancy makes the description less crisp than it could be.

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 simple two-parameter tool, the description covers the core behavior and the recipient restriction. But it omits practical context such as whether the domain must already be verified, whether the smoke requires an active domain owned by the organization, and what response the agent should expect.

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?

The schema already provides 100% coverage for both required parameters, so the baseline is 3. The description adds no parameter-specific meaning beyond the schema, such as how organization_id and domain_id relate to verified domains.

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 one controlled smoke' to a server-side secret recipient, which clearly identifies the tool's function. It emphasizes that no recipient argument is accepted, distinguishing it from general send tools. However, 'smoke' is used as jargon without being spelled out as a smoke test, and no sibling tool is explicitly named.

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 explains a critical constraint (never accepts a recipient) and the abuse-prevention rationale, but gives no explicit guidance on when to use this tool versus alternatives like commsharbor_marketing_smoke or commsharbor_message_send. No conditions, prerequisites, or exclusion criteria are provided.

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