bandwidth_node_users

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds nothing beyond that — it does not say the result is a ranking of top users, whether topUsersLimit truncates results, or how the start/end window is interpreted. With annotations carrying the safety profile, the remaining behavioral burden is unaddressed.

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?

A single short phrase, so nothing is wasted and the keying parameter is front-loaded. But its brevity is under-specification rather than discipline — the phrase carries too little information to be a useful definition.

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 4-parameter, 3-required analytics tool with no output schema and only 50% schema coverage, the description leaves the return shape (top-users list?) and the meaning of topUsersLimit and the date window unstated. Too incomplete for the tool's complexity.

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 description coverage is only 50%: uuid and topUsersLimit have no schema descriptions. The description only gestures at the uuid parameter ("by Node UUID") and says nothing about topUsersLimit's role in limiting/ranking returned users, which is the one parameter that most changes behavior.

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?

"Get Node Users Usage by Node UUID" names a verb and resource and keys it to the node UUID parameter, so the basic operation is inferable. However, "Node Users Usage" is vague — it does not say the usage is bandwidth, nor does it distinguish this from siblings like bandwidth_nodes_usage or bandwidth_user_usage, so an agent cannot confidently pick it without reading the schema.

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 when-to-use guidance at all: no mention of the date-range requirement, how it differs from bandwidth_nodes_usage (whole-node) or bandwidth_user_usage (per-user across nodes), and no exclusions. The agent must infer selection entirely from the name.

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