send_dm

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

Without annotations, description discloses it sends a private message and warns of anti-spam consequences. Lacks details on failure modes, character limits, or response format.

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?

Very concise: 5 sentences front-loaded with action and warning, followed by a clear bullet list of parameters. 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?

Covers essential behavior, parameter details, and anti-spam risk. Output schema exists so return values not needed. Minor lack of error handling info, but overall sufficient.

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?

With 0% schema coverage, description fully compensates by explaining screen_name (without @), text (required, non-empty), and optional media_id. All parameters are clearly documented.

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 it sends a private DM to a user by screen name. It distinguishes from siblings like send_dm_to_group and delete_dm.

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?

Explicitly warns against bulk calling and mentions anti-spam suspension risk. Provides clear usage context but doesn't compare with sibling tools like send_tweet.

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