get_company_balance

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

No annotations are provided, so the description carries full burden. It mentions a return ('Company balance information') but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires specific permissions, rate limits, or what format the balance information comes in (e.g., numeric value, structured object).

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 brief (two sentences) but could be more front-loaded. The first sentence states the purpose, but the second ('Returns: Company balance information') is redundant and doesn't add value beyond what might be inferred. It's concise but not optimally structured.

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 complexity (financial data tool with no annotations and no output schema), the description is incomplete. It doesn't explain what 'balance' entails, the data format, or any prerequisites. For a tool in a financial system with many siblings, more context is needed to ensure correct usage.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's appropriate here. Baseline is 4 for zero-parameter tools as they require minimal parameter explanation.

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 the tool's purpose ('Get the current balance of the company') which is clear but generic. It doesn't distinguish this from other financial tools like 'get_company_details' or 'get_company_tax_statistics', nor does it specify what 'balance' means in this context (e.g., cash balance, accounting balance, etc.).

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_company_details' and 'get_company_tax_statistics', the description doesn't clarify if this is for real-time vs. historical data, or if it's part of a broader financial reporting workflow.

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