get_fixed_asset_transactions

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

With no annotations provided, the description carries the full burden of disclosure. It names the returned attributes and 'Get' implies a read-only operation, but it does not explicitly state a safe/read-only nature, pagination behavior, ordering, or error handling. It adds some behavioral context but leaves significant gaps uncovered.

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 front-loads the verb and object and then provides the concrete scope and output fields. Every word contributes value, and there is no repetition of the tool name or schema information.

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?

The tool has 6 parameters but only one required, and 83% schema coverage plus the short description give enough for a competent agent to call it. The description covers what the log contains while the schema documents all filters; lacking is any comparison to sibling tools or output shape, but this is not critical given the high schema coverage.

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 83%, and the parameter descriptions largely speak for themselves (limit, to_date, from_date, ledger_id, transaction_type). The tool description names output fields (vendor, invoice number, amounts, dates) but adds no meaning to the input parameters beyond what the schema already provides. Baseline 3 is appropriate.

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 a specific verb (Get), resource (log of fixed asset transactions), and explicitly enumerates the transaction types (purchases, sales, disposals) and data fields (vendor, invoice number, amounts, dates). It clearly distinguishes from siblings like get_fixed_assets, which would return the asset list rather than the transaction log.

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 purpose statement implies when to use the tool (when you need a log of fixed asset purchases/sales/disposals), and the schema gives filtering options. However, there is no explicit mention of when not to use it or what alternatives like get_fixed_assets or get_ledger_statement are for, leaving the selection to inference.

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