session_user_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. 'Current account usage' implies a read-only status check but gives no detail about what usage data is included, whether it reflects the current session, or how it behaves across user/reseller/admin contexts. It is not contradictory, but it is minimal.

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, but it is under-specified rather than efficiently complete. It is a sentence fragment with no verb or structural context, so it does not earn its place as a useful tool description.

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 is simple: no parameters and an output schema is present. However, the description leaves ambiguity around whose usage is returned and gives no hint about session semantics, so an agent may not confidently select it among many similar usage-related tools.

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 tool has zero parameters and empty schema properties, so there is no parameter documentation burden. The description correctly implies no arguments are needed.

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 names a resource ('current account usage') but uses no explicit verb and leaves scope ambiguous—'account' could mean user, reseller, or admin. The tool name session_user_usage clarifies it somewhat, but the description alone does not distinguish it from siblings like users_get_usage, resellers_get_usage, or admin_usage.

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 instead of related usage or session tools. The description does not mention session context, exclusions, or alternatives, so an agent must infer suitability from the name alone.

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