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

With no annotations, the description carries the full burden of disclosing behavior. The description is essentially useless; it only repeats the name and mentions billing. There is no information about data returned, rate limits, errors, or side effects. However, it doesn't contradict annotations (since none are provided), but it fails to add meaningful 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 extremely short, which could be seen as concise, but it lacks any substantive information. It's under-specification rather than efficient communication. The structure is minimal, but given it contains almost no content, it fails to earn its place in a helpful way.

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?

The tool has a single parameter, no output schema, and no annotations, but the description provides no context about the intended use, data returned, or API-specific behavior. The sibling tools are numerous (many user-related), and this description does not help differentiate or understand the tool's role. It is completely inadequate for an agent to correctly use the tool.

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 schema defines a single 'id' string, but the description provides no additional meaning beyond the schema. With 0% schema description coverage, the description should compensate by explaining what the ID is expected to be (e.g., user's REST ID, numeric string, relationship to screen name). It does not, so the parameter semantics are unclear.

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 is minimal: 'User By Rest ID Group: User. Billing per call: 1 Credits.' It restates the tool name without explaining the specific purpose, such as fetching a user's details by their REST ID. It doesn't clearly distinguish from similar tools like get_v2_UserByScreenName or get_v2_UsersByRestIds.

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 provided on when to use this tool versus alternatives, such as using screen name instead of ID, or when multiple IDs are needed. The description only mentions billing credits, which does not help in selecting the appropriate tool.

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