fetch_transaction_stream

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

No annotations provided, so description must disclose behavior. It mentions fetching logs but does not state if read-only, pagination behavior (cursor hinted at in schema only), rate limits, or potential performance impacts for large ranges.

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?

Single sentence, front-loaded with action, no wasted words. Could be slightly improved by structuring multiple aspects, but remains efficient for its length.

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?

No annotations, no output schema, and 5 parameters with incomplete descriptions. Missing details on return format, pagination handling, and prerequisites. The description alone is insufficient for reliable tool selection.

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 coverage is 60% with descriptions for start_date, end_date, cursor. Description adds 'date range' interpretation but does not clarify the required user_id and account_id fields. Fails to fully compensate for missing schema descriptions.

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?

Description clearly states verb 'Fetches', resource 'raw transaction logs', scope 'for a date range', and purpose 'for classification and ingestion'. Differentiates from sibling tools like classify_transaction_batch and fetch_account_summary.

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?

Implies usage for raw transaction logs prior to classification/ingestion, but lacks explicit when-to-use or when-not-to-use guidance. No alternatives mentioned, leaving the agent to infer from context.

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