x_dm_conversation_events_list

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

Beyond the readOnlyHint and destructiveHint annotations, the description discloses key behaviors: default minimized event shape, the include_text flag's effect, the 30-day retention limit, and the security instruction that message bodies are third-party content to be treated as data, not instructions. This is substantial value not available in structured fields.

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?

Three dense sentences front-load the action and scope, then add constraints, output behavior, and security context without redundancy. Every sentence carries substantive information.

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?

For a list tool with an output schema present, the description covers scope, ordering, retention, default shape, optional fields, auth prerequisites, policy restrictions, and a security caveat. Nothing essential for correct invocation is missing.

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 100%, so the baseline is 3. The description adds meaningful semantic detail about include_text, explicitly describing the default minimized payload and warning about message bodies, which goes beyond the schema. It does not add much beyond the schema for page_token or max_results, which are already 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 names a specific verb ('List'), a specific resource ('direct-message events of one X (Twitter) DM conversation'), and a clear ordering ('newest first'). It also distinguishes itself from siblings like x_dm_events_list and x_dm_participant_events_list by emphasizing 'one conversation.'

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?

The description gives clear context: it is scoped to one conversation, covers at most ~30 days, and requires user-context auth plus operator opt-in. It also notes the read-only policy restriction, which is an explicit exclusion, but it does not name alternative tools or contrast when to use siblings.

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