cigchat_send_content

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

With no annotations, the description carries the full burden. It discloses that this sends a 'real message' (not a test) and requires the 'Manage Flow' scope, adding value beyond the tool name. However, it does not mention side effects, irreversibility, rate limits, or return behavior, which would be helpful for a mutating send action.

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 concise, with two sentences that front-load the purpose and include the endpoint and auth requirement. The phrase 'learn more about how to use dynamic content' is slightly vague but not wasteful. Overall, it earns its place.

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?

The tool has complex nested schemas (data.content with anyOf/not constraints) and no output schema, yet the description gives no help on constructing the data object or understanding user_ns. The auth scope and 'real message' warning add some context, but the description is incomplete for a tool of this complexity.

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 description adds no parameter-level information. Schema coverage is only 33% (only send_as_agent has a description), and both 'data' and 'user_ns' remain unexplained. The description does not compensate for the low coverage, leaving the agent without guidance on constructing the dynamic content payload or identifying the subscriber.

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 clear verb ('Send') and resource ('content to subscriber') and adds that it 'Delivers a real message to a person,' which clarifies the tool's purpose. However, it does not explicitly differentiate from sibling send tools like cigchat_send_text or cigchat_send_sms, so it stops short of a 5.

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?

There is no guidance on when to use this tool compared to the many sibling send tools. The hint to 'learn more about how to use dynamic content' implies it's for dynamic content, but no alternatives or exclusions are given. The only explicit usage context is the 'Manage Flow' scope requirement, which is a prerequisite, not a usage guideline.

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