list_scheduled_transactions

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

No annotations provided, so the description carries full burden. It does not disclose whether the tool is read-only, pagination behavior, or any auth requirements. The only behavioral content is about the exclude_fields parameter, which belongs to parameter semantics.

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 concise with a clear lead sentence and structured parameter docs. The exclude_fields explanation is slightly verbose but justified by the complex behavior. Overall, every sentence serves a purpose.

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?

Output schema is present but not shown, so we assume return values are documented. However, the description lacks info on pagination, sorting, or filtering. Given the tool has only two parameters, it feels incomplete without noting that it lists all scheduled transactions for a plan.

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%, but the description adds meaningful context: for plan_id, it suggests using list_plans; for exclude_fields, it explains the default behavior and how to override (pass [] or custom list). This compensates for the bare schema.

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 explicitly states 'List all scheduled (recurring) transactions', clearly identifying the action (list) and resource (scheduled transactions). This distinguishes it from sibling tools like get_scheduled_transaction (single) or create/update/delete variants.

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 hints at a prerequisite (use list_plans to find plan_id) but does not specify when to use this vs alternatives like get_scheduled_transaction, nor does it mention when not to use it. Usage guidance is minimal and implied from sibling names.

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