get_user

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

The description mentions the tool is for the 'current authenticated trading user', hinting at authentication but not explicitly stating requirements or side effects. Since no annotations are provided, the description should more clearly disclose that authentication is required and that the call is read-only and idempotent.

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 concise sentence that immediately conveys the action and output. No unnecessary words or repetition.

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?

For a simple tool with no parameters and no output schema, the description is adequate but could be more complete. It lists the categories of returned data but does not specify the structure or format, leaving the agent to guess the exact response shape.

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 parameter semantics are not a concern. The baseline for 0 parameters is 4; the description does not need to add parameter information.

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 precisely states the tool returns information about the current authenticated trading user, listing specific data types (permissions, activated features, RM details). It clearly distinguishes itself from sibling tools, which mostly deal with other entities like beneficiaries or trades.

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 explicit guidance on when to use the tool versus alternatives, nor any exclusions or prerequisites. The use case is implied as retrieving current user info, but the description does not mention when not to use it or contrast with other tools like get_beneficiary or get_trade.

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