get_user_requests_analytics

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the crucial behavioral detail that the tool is Enterprise-gated and returns 403 on non-Enterprise plans, which is not in annotations. No contradiction.

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 only three sentences: purpose, usage guidance with alternative, and access constraint. Every sentence is essential, no redundancy, and the most critical information is front-loaded.

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 high parameter count (29) and the presence of an output schema, the description suffices by covering purpose, usage context, and access limitations. It does not detail return values (handled by output schema) or every parameter (handled by input schema), but this is appropriate for a tool with rich structured metadata.

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 100% description coverage, so the schema fully documents all 29 parameters. The tool description does not add any parameter explanations beyond what the schema provides, which is acceptable per the baseline rule for high coverage.

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 specifies 'Get per-user request-count time-series data with counts grouped by user', which clearly states the verb, resource, and grouping. It explicitly distinguishes from the sibling 'get_users_analytics' by contrasting use cases (heavy users vs aggregate trends).

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 provides explicit guidance: 'Use this to find heavy users and traffic concentration; use get_users_analytics for aggregate active and new user trends instead.' It also discloses that the tool is 'Enterprise-gated' and returns 403 on non-Enterprise plans, helping the agent avoid errors.

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