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

No annotations are provided, so the description must disclose behavioral traits. It only mentions billing credits, which is not a behavioral aspect like auth requirements, rate limits, or side effects. The operation's read-only nature is implied by 'get' but never explicitly stated.

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 this is under-specification rather than effective conciseness. The group and billing information add little value for tool invocation, while essential details are 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?

With six undocumented parameters, no output schema, and no annotations, the description is grossly insufficient. It fails to explain what the tool returns, how to configure parameters, or when to use it, making it nearly impossible for an agent to invoke 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?

The input schema has six parameters with zero description coverage, and the description adds no meaning to any of them. Parameters like ct0, max_id, proxyUrl, and resFormat remain completely opaque, forcing the agent to guess their formats and purposes.

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 states 'get DMS List,' clearly indicating this tool retrieves a list of direct messages. However, it lacks specifics on whether it returns sent/received DMs or pagination, and it does little to distinguish itself from sibling tools like getDMS or getDMSInitIdV2.

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. The description only mentions group and billing, not any selection criteria, prerequisites, or scenarios.

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