users_get_usage

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

No annotations are provided, so the description carries the full burden. 'Live usage + limits' gives some sense of freshness and scope, but nothing about side effects, authentication needs, error behavior, or response handling is disclosed. For a read-only getter this is minimal but not wholly absent.

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 short and front-loaded, with the core purpose stated in the first sentence. It is appropriately sized for a simple one-parameter tool, though the parameter line adds little value.

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 output schema exists, so return-value documentation is not required. The tool is simple with one required parameter, but the description lacks guidance on how it relates to sibling usage tools and does not clarify semantics beyond 'account name.' It is minimally sufficient but leaves selection context to inference.

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?

Schema description coverage is 0%, so the description must compensate. It says 'username: Account name,' which adds only a synonym for the schema title 'Username' and provides no useful format, constraints, or relationship to the returned data.

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 a clear verb and resource: 'Get live usage + limits for a user.' This distinguishes it from configuration tools like users_get_config and other scope-specific tools like resellers_get_usage and admin_usage, though it does not explicitly name any sibling.

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?

There is no guidance about when to use this tool versus sibling tools such as resellers_get_usage, admin_usage, users_get_config, or users_list_all. The description only states what it does, not when to choose it over alternatives.

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