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

No annotations are provided, so the description must disclose behavioral details. It mentions a LEFT JOIN with classifications but omits rate limits, auth requirements, or any side effects. For a read operation, it is minimally transparent but insufficient for a tool with 13 parameters.

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 three sentences, front-loaded with purpose, and every sentence adds value. No redundant or filler content.

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?

Despite having an output schema, the description fails to cover most of the 13 parameters or provide usage context for common filters. The presence of a sibling tool for paged transactions suggests additional guidance is needed, which is missing.

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 8% (only npub has a schema description). The description adds meaning to session_id, unclassified_only, date_from, and date_to, covering only 4 of 13 parameters. Many parameters like limit, offset, search, category are left undocumented, inadequately compensating for the low schema coverage.

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 'Get transactions for a session with optional filters', which provides a specific verb and resource. However, it does not differentiate from the sibling tool 'taxsort_get_transactions_paged' which presumably handles pagination differently.

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 advises when to use unclassified_only and date_from/date_to, but lacks guidance on when not to use this tool or when to prefer alternatives like taxsort_get_transactions_paged. No explicit exclusions are given.

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