account_info

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

With no annotations provided, the description carries the full burden and does add value by stating 'Read-only' and 'live', which informs the agent that this is a safe, real-time query. It does not disclose output details or any rate/authentication nuance, but for a zero-parameter tool this is a reasonable level of transparency.

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 efficient sentence: it states the resource, the account scope, the live/current nature, and the read-only property. Every word earns its place and there is no fluff.

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 zero-parameter, read-only account information tool, the description tells the agent what data it will receive (account details and prepaid balance) and the operational characteristic (live, read-only). It is nearly complete; a small enhancement would be explicitly noting it returns the current INWX account balance, but nothing important is missing for invocation.

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 and schema description coverage is 100%, so there is nothing missing. Per the rubric baseline, a zero-parameter tool earns a 4 because the description is not expected to explain parameters that do not exist.

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 the exact resource ('Account details and prepaid balance of the INWX account') and clearly labels the operation as read-only. It does not start with an explicit verb like 'Retrieves', but the intent is unambiguous and distinguishes this tool from the domain/contact/nameserver siblings.

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 implies this is the tool to use when account-level details or prepaid balance are needed, and the 'live' qualifier suggests current data rather than cached values. However, it does not explicitly state when-not-to-use it or mention any alternative, though no sibling appears to overlap functionally.

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