Get a party's classified transactions

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

Discloses key behaviors: returns compact rows sorted newest-first, client-side filtering for txType over recent pages, and extra API call for includeCount. As a read-only query, no annotations are provided, but the description adequately implies safety without contradictions.

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?

Two concise sentences that front-load the main purpose and return format, then offer guidance on alternatives and optional parameter. No wasted words.

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?

Fully explains return format (compact rows with fields), sorting, and the includeCount option. Without an output schema, this is sufficient. Could mention default date ranges or pagination, but not necessary for typical use.

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 covers 100% of parameters with descriptions. The description adds minor context (e.g., classification types, client-side filtering note), but does not significantly enhance understanding beyond the schema.

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 specific verbs ('Get a Canton party's transaction history') and resources, and clearly distinguishes from sibling tool 'get_transaction' by stating 'Use get_transaction for the full payload of one update.'

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?

Provides clear context on when to use this tool vs alternatives by referencing 'get_transaction' for full payload. Also explains optional parameters like includeCount and filtering by txType, but does not explicitly state when not to use this tool.

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