users_with_most_sessions

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to do so. It doesn't indicate whether this is a read-only or mutation operation, what permissions are needed, how results are returned (e.g., sorted, limited), or any rate limits. The '[WIP]' tag suggests incompleteness but adds no useful behavioral context.

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 overly concise to the point of under-specification. While it's brief, it wastes space on '[WIP]' and redundant elements like '[Required: sessions]' without adding meaningful content. It lacks front-loaded clarity and doesn't structure information effectively for tool selection.

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?

Given the complexity implied by the tool name and sibling context, the description is completely inadequate. With no annotations, no output schema, and a parameter with 0% coverage, it fails to provide essential details about behavior, results, or usage. It doesn't help an agent understand what the tool does or how to invoke it 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 one parameter ('domain') with 0% description coverage, and the tool description provides no information about parameters. It doesn't explain what 'domain' represents, its format, or how it relates to the tool's function. With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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 '[WIP] Users with Most Sessions [Required: sessions]' is vague and tautological. It restates the tool name with minimal elaboration, only adding '[WIP]' and '[Required: sessions]' which don't clarify the specific action or resource. It doesn't distinguish from siblings like 'list_all_user_sessions' or 'users_with_most_cross_domain_sessions', leaving the purpose unclear.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions '[Required: sessions]' but doesn't explain what this means contextually or how it differs from other session-related tools in the extensive sibling list. There are no explicit instructions, prerequisites, or comparisons to help an agent choose appropriately.

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