gorelo_list_billing_roles

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

With no annotations, the description carries the burden of behavioral transparency. The verb 'list' clearly indicates a read-only operation, and the description adds no misleading claims. While it doesn't explicitly state 'does not modify data' or discuss permissions/rate limits, the simple read-only nature is self-evident from the wording, and the added usage context provides meaningful behavioral insight.

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?

Two sentences with zero waste. The first sentence states the core purpose; the second adds a critical usage tip. The description is front-loaded and every word earns its place.

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 list tool with no output schema, the description is nearly complete. It tells what the tool lists, the context (configured for the service provider), and how to apply the result (use id as BillingRoleId). It could explicitly mention that the response contains role objects with id and name, but this is a minor gap given the tool's simplicity.

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, so the baseline for parameter semantics is 4. The description adds no unnecessary parameter detail, and the schema coverage is 100% (vacuously). There is nothing here that needs compensation.

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 tool lists billing roles for the service provider, using a specific verb ('list') and resource ('billing roles'). It also immediately explains the purpose of the result (using the role's id as BillingRoleId when logging time), which distinguishes it from sibling list tools like gorelo_list_ticket_statuses or gorelo_list_clients.

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 explicitly tells the agent when this tool's output is needed: 'Use a role's id as BillingRoleId when logging time against a ticket.' It implies this tool should be called before time-entry creation, which is clear usage context. It doesn't mention exclusions or alternatives, but there are no sibling billing-role tools, so this is sufficient.

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