trigger_plaid_fetch

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

With only openWorldHint annotation, the description carries the burden: it discloses the rate limiting (60s delay) and long duration (up to 5 min), which are key behavioral traits beyond what annotations provide. No contradictions with annotations.

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?

Two sentences, no wasted words: first sentence states the core action, second adds optional scoping and important constraints. Well front-loaded.

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 three optional parameters and no output schema, the description covers the essential: what it does, optional scoping, and performance constraints. Minor omission: no mention of what happens if rate limit is hit (e.g., error handling).

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 100%, so the description adds little new meaning. It mentions scoping to date range and account ID, which paraphrases the schema. The mutual requirement of start_date and end_date is implied but not explicitly reinforced.

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 triggers a fetch of latest data from Plaid, with optional scoping to date range or specific account. This verb+resource combination is distinct from siblings which are mostly read or manage operations on existing data.

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 notes the 60-second delay and up to 5-minute fetch time, setting expectations. However, it does not explicitly contrast with alternative tools like get_all_plaid_accounts (which is read-only) or when not to use this tool.

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