camelot_crypto_tax_calculator

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

Annotations already mark the tool as idempotent and non-destructive, so the description does not need to repeat safety behavior. It adds a meaningful behavioral fact—'Local browser processing'—which implies no server-side persistence or upload, plus the FIFO/LIFO calculation behavior. This goes beyond the structured fields without contradicting them.

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 and front-loaded: the core function and method appear in the first sentence, followed by the local-processing note. The canonical URL and double period are minor blemishes, but the overall length is appropriate for a one-parameter calculator.

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 a single fully documented parameter, an output schema, and annotations covering idempotency/destructiveness, the description covers most operational basics. The main gap is that FIFO/LIFO is advertised but no schema field or explanation shows how an agent selects between them; otherwise the tool is adequately specified.

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 input schema already has 100% field-level documentation for the single trades parameter, so the baseline is 3. The description adds no extra parameter syntax or examples, and its mention of FIFO/LIFO is not tied to a schema field, so it neither improves nor harms parameter understanding.

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 opens with a specific noun phrase and verb—'Track crypto capital gains and losses'—and names the exact methods (FIFO and LIFO). This gives an agent a clear, distinct purpose: crypto capital-gains tax calculation rather than a generic tax estimate. The specificity separates it from the many financial sibling tools even though no sibling is named.

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 intended use is implied by the domain: when an agent needs FIFO/LIFO crypto capital-gains/loss tracking, this is the tool. However, the description does not state when to prefer it over camelot_tax_estimator or other finance calculators, nor does it list exclusions such as 'not for tax filing.'

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