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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it reveals nothing about side effects, authentication requirements, expected behavior, or required context. Sending a DM likely involves account actions, but the description does not disclose anything beyond the tool name.

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 short, but this is under-specification rather than conciseness. 'Group: DMS' and 'Billing per call' add no functional value, and the essential purpose is missing.

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?

This is a 10-parameter DMS-sending tool with no annotations, no output schema, and almost no parameter documentation. The description completely fails to provide the contextual information needed for an agent to invoke this tool correctly.

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 only 10%, with 10 parameters and zero required. The description adds no meaning to any parameter, leaving the agent to guess what fields like ct0, resFormat, proxyUrl, or recipient_ids actually mean.

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 merely restates the tool name ('sendDMSV2') and category ('Group: DMS'), but never explicitly states that it sends a direct message. It provides no meaningful verb-resource clarity and does not distinguish it from sibling tools like sendDMS or sendDMSMedia.

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?

There is no guidance on when to use this tool versus alternatives such as sendDMS, sendDMSMedia, or getUpdateDMSV2. The description only mentions billing, which is irrelevant to usage context.

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