cm_resend_transactional_message

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

Annotation destructiveHint=true flags potential side effects. Description adds that it returns a new message ID, but doesn't disclose if original message is modified, if charges apply, or error handling. Some value beyond annotation.

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?

Single sentence with warning emoji, no wasted words. Front-loaded with purpose and output hint. Appropriate size for a simple tool.

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?

Covers core purpose and output for a straightforward resend operation. Lacks details on prerequisites, error cases (e.g., if messageID invalid), or rate limits. Minor gaps but adequate for the tool's simplicity.

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%, and description of messageID ('Transactional message ID to resend') mirrors schema description. No additional semantic value added beyond what schema already provides.

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?

Description clearly states verb 'Resend', resource 'transactional message', and mentions output 'returns a new message ID'. Distinct from siblings like cm_get_transactional_message and cm_list_transactional_messages.

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?

Implies usage when needing to resend a specific message, but no explicit guidance on when not to use or alternatives like sending a new message. No usage context provided.

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