Get Scheduled Transactions

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, ensuring the agent knows it's safe. The description adds that filters are optional but does not disclose return format, pagination, or ordering, providing only marginal additional transparency.

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, consisting of a single sentence with no redundant information. However, it could be slightly more informative without adding length, e.g., mentioning that results are returned in a list format.

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?

The tool has no output schema, and the description does not explain the structure of the response or any limitations like pagination. For a retrieval tool with multiple optional filters, this leaves significant gaps in understanding 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?

Schema coverage is 60% with three of five parameters described. The description adds meaning to account_id and category_id by labeling them as filter options, but does not cover the date range parameters (due_after, due_before) or budget_id in detail. It thus provides some semantic value beyond the schema but not fully comprehensive.

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 verb 'Get' and resource 'scheduled transactions', indicating retrieval. It mentions optional filtering, but does not explicitly differentiate from sibling tool 'search_transactions' which might also list scheduled transactions. However, the name and context are sufficient for basic understanding.

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 over alternatives such as 'search_transactions' or 'list_undo_history'. The description lacks any contextual cues for selection.

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