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

With no annotations, the description should disclose side effects, safety, or auth requirements. It mentions needing auth_token and ct0 and billing per call, but does not describe any behavioral traits such as whether it is read-only, what it returns, or any side effects.

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 unstructured, mixing links, auth tips, and billing info. It is not concise in a useful way because the essential purpose is missing; the content is mostly extraneous.

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 tool is complex (6 params, no output schema, no annotations) and the description fails to provide necessary context like what the tool does, expected inputs, or return value. It is critically incomplete.

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% and the description does not explain any of the six parameters. It only obliquely references auth_token and ct0 without describing their format or purpose.

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 does not state the tool's function; it only provides external links and authentication instructions. The name suggests getting DMs, but the title 'receiving events' is ambiguous and does not clarify the resource or action.

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 is given on when to use this tool versus many sibling tools like getDMSListV2 or sendDMS. There is no mention of alternative tools or decision criteria.

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