fixed_asset_accounting__double_declining_schedule

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

The description mentions the residual floor behavior, but with no annotations, it fails to disclose other traits like return format, error handling, or assumptions (e.g., if cost <= residual).

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 single sentence is concise, but it is overly brief for a tool with no param descriptions. Front-loading the domain tag helps, but lacks structure.

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?

For a 3-parameter tool with no output schema, the description partially covers purpose and a key constraint, but misses param details, return value, and edge cases. Incomplete for an agent to invoke reliably.

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 coverage is 0%, and the description adds no meaning to the three parameters (cost, residual, life_years). Units, expected ranges, and usage are absent.

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 it computes annual double-declining balance (DDB) charges and notes the residual constraint. This distinguishes it from other depreciation methods, though it doesn't explicitly name siblings.

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 on when to use DDB vs straight-line or units-of-production. No exclusions, prerequisites, or context for decision-making.

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