get_user_info

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

No annotations are provided, so the description bears full responsibility. It states the tool returns data but fails to disclose behavioral traits such as whether it requires authentication, rate limits, or side effects. The mention of an internal version is helpful but insufficient.

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, short sentence that is concise and placed first. It contains no unnecessary words, but could be more informative without becoming verbose.

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 no parameters and an output schema (though its content is unknown), the description is minimally adequate. It explains the tool's output at a high level, but does not clarify what specific stats are returned, leaving potential users uncertain about its relevance.

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 zero parameters, so no parameter descriptions are needed. According to guidelines, 0 parameters yields a baseline of 4. The description does not add param info, but none is required.

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 states it returns account usage/stats info and mentions an internal data source ('analytic-v2 userStats/user-info'), making the purpose clear. However, it does not specify exactly which stats, leaving some ambiguity. The sibling get_usage_stats may overlap, but the description distinguishes by referencing a specific endpoint.

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 siblings like get_usage_stats or get_current_user. The description offers no context about appropriate use cases, prerequisites, or alternatives.

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