get_transactions_needing_review

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

With no annotations, the description carries the full burden for behavioral disclosure. It only mentions 'compact format by default', implying a verbose option, but does not explain pagination, ordering, date filtering, or what 'needs review' means in terms of status. The read-only nature is implied by 'get', but other behaviors are unexplained.

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 short sentences, front-loaded with the core purpose and a useful default behavior. Every word earns its place, with no fluff or repetition.

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 four optional parameters and no annotations or output schema, the description should clarify the meaning of 'all', the effect of date ranges, limit behavior, and what fields appear in compact vs verbose mode. It does none of this, leaving the agent to infer crucial invocation details.

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 0%, so the description must compensate for all four parameters (limit, verbose, start_date, end_date). It only hints at 'verbose' via 'compact format by default' and says nothing about the other parameters. This is insufficient.

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 phrase 'Get all transactions that need review' clearly identifies the tool's function and distinguishes it from generic transaction retrieval tools like get_transactions. The resource ('transactions') and state ('needing review') are explicit, though the scope of 'all' (accounts, date ranges) is not specified.

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 alternatives such as get_transactions, search_transactions, or get_categorization_suggestions. It does not state whether it includes all accounts or if it should be used alongside review-related tools.

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