rm_list_user_bill_rates

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

The annotations already signal readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds no additional behavioral context beyond what annotations and the tool name already communicate, such as pagination, ordering, or error behavior.

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 with no filler. Every word contributes meaning, and it is as concise as a simple list operation should be.

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 one-parameter read-only list with an output schema and safety annotations, the description is minimally adequate. It lacks context about what 'bill rate tiers' represents and provides no guidance on user_id format, but the output schema likely covers return structure.

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?

With 0% schema description coverage, the description must compensate for parameter documentation. It only reuses the concept of 'user' already visible in the property name user_id, providing no extra meaning about accepted formats, requiredness context, or examples.

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 states a specific action ('List'), a specific resource ('bill rate tiers'), and a clear scope ('for a user'). This clearly distinguishes it from the related sibling rm_create_user_bill_rate and from other list tools in the set.

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?

Usage is implied: if an agent needs to see a user's bill rate tiers, this is the tool. However, the description provides no explicit when-to-use guidance, no mention of alternatives, and no context about when not to use it.

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