billy_get_account

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

The description explicitly states 'READ-ONLY', indicating no side effects, which is critical for a get operation. However, with no annotations provided, the description carries the full burden; it lacks details on permissions, rate limits, or error handling, but the read-only claim provides adequate transparency for a simple fetch.

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 at three words: 'Fetch one account. READ-ONLY.' It is front-loaded with the core purpose and includes a critical behavioral note. Every word earns its place with no redundancy.

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 (one required param, no output schema), the description is minimally sufficient but lacks detail on return format or error conditions. It meets the basic need but does not add extra context that would be helpful for an agent, such as what account fields are returned.

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 single parameter 'id' has 0% schema description coverage, but its name is self-explanatory. The description does not elaborate on format or constraints, but the schema already defines it as a required string. Baseline score of 3 is appropriate since the parameter is straightforward.

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 'Fetch' and the resource 'one account', making the tool's purpose unambiguous. It distinguishes itself from siblings like 'billy_get_bank_account' or 'billy_list_accounts' by specifying a single account fetch.

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. It does not mention when-not to use it or point to siblings like 'billy_list_accounts' for broader queries.

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