bandwidth_stats_nodes_get_stats_nodes_users_usage

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

No annotations are provided, so the description carries full behavioral burden. It reveals the HTTP verb and path (POST) and a pagination note about 'start', but never explains the confirmation/preview behavior of this non-GET operation, rate limits, or auth needs. The safety-relevant behavior is hidden in the schema, not the description.

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?

It is short, but front-loaded with an HTTP method/path and a 'Tags:' dump rather than the tool's purpose. The trailing Russian pagination sentence is oddly placed and low-value, so structure is poor even though word count is low.

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 5-parameter, nested-body POST tool with no annotations and no output schema, the description is inadequate. It omits the confirm requirement, the body structure (nodesUuids), date-range semantics, and return shape, leaving the agent under-informed.

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 only 60% and topUsersLimit has no description anywhere. The description only mentions pagination via 'start', which actually conflicts with the schema's date-typed start parameter, adding confusion rather than clarity for end, confirm, and topUsersLimit.

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 line 'Get Nodes Users Usage by Nodes UUIDs' largely restates the tool name and offers no specificity beyond 'by Nodes UUIDs'. It is nearly indistinguishable from siblings like bandwidth_stats_nodes_get_node_usage and bandwidth_stats_nodes_get_stats_node_users_usage, and an agent cannot tell which stat this returns.

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 the many near-identical bandwidth-stats siblings. No prerequisites, no mention of the required confirm flag, nothing that would route an agent correctly.

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