Send a direct message

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

Annotations already indicate destructiveHint=true, so the description does not need to reiterate mutability. It adds value by specifying that the DM is sent from a connected Upload-Post profile and the recipient_id must come from Instagram comments or DM conversations, providing useful behavioral context beyond the annotations.

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, front-loading the purpose and essential usage context. Every sentence adds value without redundancy.

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 the presence of an output schema, the description does not need to explain return values. It adequately covers the purpose, source profile, and recipient ID origin, making it complete for the send action.

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 100%, but the description adds context about the recipient_id (returned by Instagram comments/DM tools) and identifies the user parameter as the Upload-Post profile name. This enhances understanding beyond the schema definitions.

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 clearly states the action (Send), resource (Instagram DM), and source profile (connected Upload-Post profile). It effectively distinguishes the tool from siblings like reply_to_comment by specifying the use of a recipient_id from comments or DM conversations.

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 provides clear guidance on when to use the tool (send DMs) and hints at the source of the recipient_id. However, it lacks explicit exclusions or comparisons with sibling tools that might be alternatives for similar tasks (e.g., create_comment, reply_to_comment).

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