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

No annotations are provided, so the description carries full burden. It does not disclose any behavioral traits: no mention of side effects (sending a DM), rate limits, authentication requirements beyond the links, or response behavior. The description is essentially a stub with external links.

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 extremely short, but it is under-specified rather than concise. It contains external links and a billing note, but no substantive content. The structure is poor: it starts with a link, then a question, then a group label, then billing. It does not front-load the purpose.

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 8 parameters, no annotations, no output schema, and no parameter documentation, the description is completely inadequate. It provides no information on how to construct a request, what the response looks like, or any operational details. The external links are not a substitute for inline documentation.

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 0%, and the description provides no parameter explanations. The 8 parameters (ct0, text, type, apiKey, proxyUrl, resFormat, auth_token, recipient_id) are completely undocumented. The description does not even hint at what each parameter means or how they relate to the API call.

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 is minimal and vague: 'sendDMS events.' It does not clearly state what the tool does (e.g., 'Send a direct message to a user'). The name 'post_base_apitools_sendDMS' suggests sending DMs, but the description adds no clarity. It fails to distinguish from siblings like sendDMSV2 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?

No guidance on when to use this tool vs alternatives. The description only provides external links for API details and auth token acquisition, but no context on use cases, prerequisites, or exclusions. Siblings like sendDMSV2 and sendDMSMedia exist, but no differentiation is provided.

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