billy_list_tax_rates

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

No annotations are provided, so the description carries the burden of behavioral disclosure. The 'READ-ONLY' label indicates no side effects, which is helpful. However, it does not disclose other traits such as pagination, authentication requirements, or rate limits. The description is adequate but not thorough.

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 extremely concise: two short sentences with no wasted words. It front-loads the core purpose and immediately adds a behavioral tag. Every sentence 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?

Given the tool's simplicity (no parameters, no output schema), the description is largely complete. It states what the tool lists. However, it lacks specifics about the output format or scope (e.g., whether it lists all tax rates from the entire organization). Still, for a straightforward list, it meets the minimum bar.

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, so the input schema provides complete definition. According to guidelines, baseline for 0 parameters is 4. The description adds no parameter information, which is acceptable as there is nothing 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 'List configured tax rates' uses a specific verb ('List') and resource ('tax rates'), clearly indicating the tool's function. The 'READ-ONLY' tag reinforces the read-only nature. It distinguishes itself from sibling list tools by targeting a specific entity.

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 provides no guidance on when to use this tool versus alternatives (e.g., other list tools like billy_list_accounts). There is no mention of context, prerequisites, or exclusion criteria, leaving the agent to infer usage from the resource name alone.

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