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

No annotations are provided, so the description carries the full burden. It only lists what is returned, but does not disclose behavioral traits such as whether the operation is read-only, requires specific permissions, is computationally expensive, or is idempotent. The mention of 'base currency' adds minimal transparency.

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 sentence that is front-loaded with the key outputs (Net worth, balance sheet, current holdings). It contains no redundant information and is highly efficient.

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 that there are no parameters and no output schema, the description covers the essential information: what the tool returns. It does not specify the format or structure of the output, but for a simple dashboard snapshot, the description is reasonably complete. A higher score would require mention of whether the balance sheet includes all accounts or just a subset.

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 no parameters, so the description does not need to explain parameter meanings. Schema description coverage is 100% trivially, and the description adequately describes what the tool does without parameter context. Baseline of 3 is exceeded because no parameters need 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 that the tool returns net worth, balance sheet, and current holdings in the ledger's base currency. This distinguishes it from siblings like get_net_worth_history (historical data) and get_tax_report (tax-specific). The verb 'get' plus specific resources (net worth, balance sheet, holdings) makes purpose unambiguous.

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 implies usage for a current financial snapshot but does not explicitly state when to use this versus alternatives like get_net_worth_history for historical trends or list_transactions for transaction-level details. No exclusions or prerequisites are mentioned.

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