get_user_usage

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. It states 'admin only' (authorization) and 'Get' (read operation), but lacks details on what the statistics include, potential side effects, rate limits, or data freshness. This minimal transparency is insufficient for a tool without 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?

The description is a single, focused sentence that immediately conveys the core purpose and key constraint (admin only). No extraneous text, front-loaded with essential information.

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?

Despite clear parameter schemas, the description fails to specify what usage statistics are returned (e.g., metrics like pageviews, sessions) or how date range parameters affect results. With no output schema, this gap is significant for an agent needing to interpret the response.

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% coverage with descriptions for all parameters, rendering the description redundant for parameter meaning. The description adds no extra context beyond the schema, earning a baseline score of 3 as per guidelines.

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 clearly states the verb 'Get' and resource 'usage statistics for a specific user', with an admin restriction. It is specific enough to distinguish from sibling tools like get_user (which retrieves user profile) and get_stats (which might be general), but does not explicitly differentiate from potential other usage stats 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?

The description only notes 'admin only', which is an authorization constraint but offers no guidance on when to use this tool versus alternatives. For example, there is no mention of alternatives for aggregated usage or non-admin scenarios, leaving the agent to infer context from sibling names.

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