Finances_listTransactions

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool executes in a separate Kuundo deployment, which is useful, but it leaves out expected behavior such as return format, pagination, authentication needs, or side effects. The agent is left guessing what will happen after invocation.

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 very short and contains no redundant filler beyond the 'Catalog entry' phrase. The deployment context is front-loaded and the functional statement is direct. It could be criticized for being terse, but as far as conciseness, it is efficient.

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?

This tool has no annotations, no output schema, and an effectively empty input schema, so the description needed to compensate with a complete operational picture. It does not: parameter names, return shape, error conditions, and relationship to sibling finance tools are all missing. An agent cannot reliably select or invoke this tool based on this definition.

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 is empty with additionalProperties allowed, and the description only says 'for the given parameters' without naming or explaining any parameter. Since there is no schema property documentation, the description was the only chance to convey parameter meaning, and it fails to do so. An agent cannot know what inputs are valid or required.

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 tool's function: 'Returns transactions for the given parameters.' This provides a specific verb ('Returns') and resource ('transactions'). However, it does not differentiate this from numerous sibling tools that also list financial data, such as FinancesV0_listFinancialEvents or SellerWallet_listAccountTransactions.

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 offers no explicit guidance on when to use this tool over alternatives. It mentions that it 'Runs in your Kuundo deployment, not here,' which hints at a deployment context, but it does not state the conditions for selecting this tool, prerequisites, or exclusions relative to similar listing tools.

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