rh11_account_get

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

The description is consistent with the readOnlyHint annotation and adds value by enumerating the returned fields (email, name, company, plan, account type). This defines the tool's observable behavior beyond simply stating it is a 'get'. It does not cover auth or response details, but for a simple no-parameter read, the field enumeration is sufficient.

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, front-loaded sentence that names the verb and resource immediately. It contains no filler and every word contributes to understanding the tool's purpose.

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 no-parameter, read-only getter, the description fully covers what the tool does and what data it returns. The explicit field list mitigates the absence of an output schema, and the sibling list provides sufficient context for distinguishing it from related account 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?

There are zero parameters, so the schema places no semantic burden and the baseline is 4. The description's field list indirectly clarifies what output to expect, which helps compensate for the lack of an output schema, though there is no parameter-specific detail to add.

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 uses a specific verb ('Get') and clearly identifies the resource ('Rhodium11 account info') along with a field list. This distinguishes it from sibling tools like rh11_account_get_subscription and rh11_account_get_service_rates, which target more specific data.

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 for retrieving general account-level information (email, name, company, plan, account type), providing clear context. However, it does not explicitly state when to use this over related account getter tools, so the guidance is implicit rather than explicit.

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