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

The description adds important behavioral context beyond the annotations: it is idempotent, it confirms target and time, and it does not return a message id or echo the body. This aligns with idempotentHint=true and destructiveHint=true without contradiction. It could also mention permission requirements, but the 'organization-owned' qualifier partially covers this.

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 two tightly written sentences, with the primary purpose front-loaded and the key idempotency caveat in the second. There is no fluff or repetition, and every sentence adds value.

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 send operation, the description covers purpose, idempotency, return behavior, and ownership constraint, while annotations handle side-effect hints and the output schema handles return details. Minor gaps remain around permission prerequisites and error handling, but these are not critical given the existing structured information.

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 100%, yet the description enriches parameter meaning: it clarifies that idempotencyKey must be reused only for identical conversation and text, and that conversation must be organization-owned, which is not explicit in the schema. This goes beyond the schema's descriptions by adding usage constraints tied to parameters.

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 uses a specific verb-resource pair, 'send one exact operator reply in an organization-owned Supovia conversation', which clearly differentiates it from read-only siblings like get_conversation and list_conversations. It also states the scope ('organization-owned') and the message type ('operator reply'), leaving no ambiguity about what the tool does.

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 clear guidance on idempotency key reuse ('Reuse the same idempotencyKey only when retrying the same conversation and text'), but it does not explicitly state when to choose this tool over alternatives or when not to use it. The context implies it is for sending operator replies, yet no exclusions or sibling comparisons are provided.

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