pocketsmith_list_transactions_by_account

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

With no annotations, the description reveals that transfers are excluded by default and filters are available, but lacks details on pagination, result ordering, or read-only nature.

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 two concise sentences with no unnecessary words, front-loading the core action and key behavioral note.

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 10 parameters, no output schema, and no annotations, the description covers the basic filter options and default behavior but omits important context like pagination, error handling, or result format.

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?

All 10 parameters have schema descriptions (100% coverage), so the description adds little beyond highlighting the default exclusion of transfers; no additional syntactic or semantic detail is provided.

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 the verb 'List' and the resource 'transactions for a specific account', and distinguishes from siblings by specifying account-level filtering and default transfer exclusion.

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 indicates the tool is for listing transactions for a specific account, but it does not provide explicit guidance on when to use this tool over alternatives like pocketsmith_list_transactions_by_category or pocketsmith_search_transactions.

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