thryx_balance

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

With no annotations, the description carries the burden of behavioral disclosure. It states the requirement for THRYX_API_KEY (auth) and equivalence to GET /api/agent/home, implying a read-only operation. It also mentions the 'recommended next-action' feature, adding context beyond simple balance retrieval. This is good but does not describe error behavior or output format, so not a 5.

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 exceptionally concise: two sentences, roughly 20 words, front-loaded with the core purpose. Every sentence earns its place, including the API key requirement and the endpoint equivalent. No redundant or vague wording.

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?

Given the tool's low complexity (zero parameters, no output schema), the description is remarkably complete. It specifies the exact outputs (ETH, THRYX, total value, recommended next-action), the prerequisite (API key), and the underlying HTTP method. An agent can confidently select and invoke this tool without further clarification.

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, so schema coverage is 100%. The baseline for 0 params is 4. The description adds no parameter-specific information, but none is needed. The mention of outputs (ETH, THRYX, total value, next-action) provides some semantic context about what the returned data will contain.

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 clearly states what the tool does: it returns the wallet balance including ETH, THRYX, total value, and a recommended next-action. This is a specific verb+resource description that distinguishes it from sibling tools like thryx_portfolio or thryx_info by focusing on the balance and a suggested action.

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?

The description provides clear context for when to use the tool: when needing wallet balance information. It also implicitly excludes write actions by mentioning it is equivalent to a GET request, but does not explicitly name alternatives or when-not-to-use. The API key requirement is a useful prerequisite, though no explicit 'instead of' guidance is given.

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