getTransactions

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

The description discloses the exclusion of pending transactions but omits other important behaviors such as pagination, rate limits, or authentication requirements. Since no annotations are provided, the description carries the full burden and falls short.

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 a single, efficient sentence with no redundant or extraneous information. It is front-loaded with the core function and immediately useful.

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 the absence of an output schema, the description should provide more context about return format, pagination, and limitations. With 5 parameters and no output schema, the current description is inadequate for agents to fully understand the tool's behavior.

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?

With 100% schema description coverage, the parameters are already well-documented in the schema. The description adds no additional semantic value beyond stating the overall purpose. Baseline score of 3 is appropriate.

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 returns plan transactions and excludes pending ones. It distinguishes from sibling getters that filter by account, category, etc., though it does not explicitly list the filtering capabilities covered by optional parameters.

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?

No guidance is provided on when to use this tool versus more specific alternatives like getTransactionsByAccount or getTransactionsByCategory. Without such context, agents may underutilize or misuse the tool.

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