twitter_x_user_stream_list_users

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

Beyond the readOnlyHint and destructiveHint annotations, the description honestly documents that x_user_id is always null and is_monitor_profile is always 0, plus 'Free per call.' This is rich behavioral context and does not contradict any annotations.

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 short sentences: the core purpose in the first, important field caveats in the second, and cost in the third. It is front-loaded and contains no filler.

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?

There is no output schema, so the description carries the burden for return behavior. It explains key envelope fields and the monitoring scope, but does not enumerate the full output shape or pagination; still sufficient for a zero-param list tool.

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 tool has zero parameters, so the baseline is 4. No parameter documentation is needed, and the description adds useful output-field semantics instead.

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 uses a specific verb and resource: 'list every account you are currently tweet-monitoring.' It also explicitly positions itself as a 'Compat drop-in for twitter_monitor_list', which distinguishes it from sibling list/add/remove tools.

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?

'Compat drop-in for twitter_monitor_list' gives clear context that this is the x_user_stream-shaped replacement for that sibling tool. It implies when to use it relative to the native monitor list, though it does not spell out when not to use it.

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