status

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

No annotations provided, so description carries full burden. It successfully discloses what data is retrieved (balance, positions, orders) in lieu of an output schema. However, it omits details on data freshness, caching behavior, or whether this requires authentication.

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?

Single sentence with zero waste. Information is front-loaded (verb first) and the colon-delimited list efficiently communicates the data scope without redundant phrasing.

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 read-only status tool with no parameters, the description adequately compensates for the missing output schema by enumerating the specific data returned (balance, positions, orders). Minor gap regarding real-time vs. cached data prevents a 5.

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?

Input schema has zero parameters. Description correctly mentions no parameters and focuses entirely on return value semantics. Baseline 4 applies for zero-parameter tools.

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?

Specific verb ('Get') + resource ('agent's current status') with explicit scope (balance, active positions, open orders). Clearly distinguishes from action-oriented siblings like 'bet', 'cancel', and 'register' by indicating this is a state retrieval operation.

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?

Provides clear context by listing the specific data domains returned (balance, positions, orders), implying usage for financial/position state checks. Lacks explicit when-not guidance or named alternatives, but the content makes the use case obvious.

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