List funding instruments

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that: no mention that this is scoped to a single ad account, no pagination expectations, no note that the ad_account_id may default from an environment variable. It essentially restates the title.

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?

A single economical sentence, front-loaded with the action and resource. Nothing is wasted, though there is also very little there.

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?

For a 10-parameter, zero-required, no-output-schema listing tool with three sibling funding-instrument tools nearby, this definition is far too thin. An agent is left to reverse-engineer filtering, time-range, and pagination behavior from the schema alone, with nothing explaining account scoping or default resolution.

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?

Ten parameters with only 60% schema description coverage, and the description mentions no parameters at all. Several parameters are entirely undocumented in both places (mode enum, search, start_time/end_time), so the description does not compensate for the coverage gap as it should.

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?

States a specific verb (List) and resource (funding instruments) and even parenthetically defines the resource as payment methods and credit lines, which helps an agent who doesn't know Reddit Ads terminology. It does not, however, distinguish itself from the sibling reddit_ads_query_business_funding_instruments, which an agent could easily confuse this with.

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?

There is no statement of when to use this tool versus the closely named reddit_ads_query_business_funding_instruments or the related reddit_ads_list_funding_instrument_allocations. No prerequisites, no context on account scoping beyond the schema's default-value note.

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