get_general_ledger

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says "Get the general ledger report" and does not mention read-only behavior, default basis, date filtering, zero-balance handling, precision defaults, or response characteristics. The word "Get" weakly implies retrieval, but this is not meaningful behavioral disclosure.

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 short and front-loaded, but it is under-specified rather than appropriately concise. One generic sentence does not earn its place for a report tool with eight parameters and several sibling reports.

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?

With no annotations, no output schema, eight optional parameters, and many sibling report tools, this description is incomplete. An agent has no information about defaults, filtering semantics, or what differentiates this report from similar financial reports.

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?

Schema description coverage is only 25%, yet the description adds no meaning for any parameter. It does not explain noneZero, showZero, noneTransactions, accountIds, basis, or precision, leaving an agent without enough information to choose or combine these filters correctly.

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 uses a clear verb and resource: "Get the general ledger report." This unambiguously identifies the action and object, but it does not distinguish this from sibling report tools like get_trial_balance or get_profit_loss, so it lacks sibling differentiation.

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?

There is no guidance about when to use this tool versus alternatives such as get_trial_balance, get_profit_loss, or get_balance_sheet. The description only states what the tool does, with no context, exclusions, or alternative routing.

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