Send DM

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

With destructiveHint=true and openWorldHint=true, the description adds context by explicitly labeling the operation as a write operation and requiring confirm_send to actually send. It also describes the return dict. This goes beyond repeating annotations, though it could mention consequences of confirm_send=False.

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 well-structured with a clear purpose line, a warning about confirm_send, and a concise Args/Returns breakdown. Every sentence serves a purpose without wasted words.

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 description covers the core behavior, parameters, and return value, but does not address edge cases like what happens when confirm_send is False or potential errors. Given the output schema exists, this is acceptable, but there is room for more context.

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 0%, but the description provides a detailed Args section explaining each parameter's meaning, including the required confirm_send flag and the internal ctx context. This fully compensates for the schema's lack of descriptions.

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 tool's function with specific verb ('Send') and resource ('direct message to an Instagram user'), distinguishing it from sibling tools like get_direct_inbox and get_dm_conversation that read 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?

The description implies usage for sending DMs but does not explicitly mention alternatives or when-not-to-use scenarios. It only notes that confirm_send must be True, which is a safety gate rather than a usage guideline.

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