rh11_account_get_service_rates

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

Annotations include readOnlyHint=true, so the description only needs to add context beyond that. It does so by disclosing the 'empty object if no plan is active' behavior, which is useful and not apparent from the annotation. No contradictions exist with the annotations.

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 sentence, directly front-loaded with the purpose and a useful edge case. Every word earns its place, with no filler or redundant information.

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 simple nature of the tool (no params, no output schema), the description is largely complete. It states what the tool does and one important return condition, which partially compensates for the lack of an output schema. However, it does not describe the structure of the returned rates object, so completeness is slightly below perfect.

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 and schema description coverage is 100% (vacuously). As per guidelines, 0 params receives a baseline of 4. The description adds no parameter information, but none is needed.

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 the verb 'Get' and the resource 'Rhodium11 service pricing rates', making the tool's purpose immediately obvious. It also adds a behavioral detail (returns empty object if no plan is active) that further distinguishes it from sibling account tools like rh11_account_get_subscription.

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 usage for checking current service rates but does not explicitly state when to use it versus alternatives such as rh11_account_get_subscription. It provides context (current rates, empty if no plan) but lacks explicit when-not or alternative guidance.

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