list_budget_schedules

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

With no annotations, the description carries full burden. While it mentions pagination, it does not disclose other behaviors like default ordering, whether inactive schedules are included, rate limits, or error handling. The 'paginated results' is minimal context.

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 short sentences, no wasted words. First sentence defines purpose, second adds key behavioral detail (pagination). Highly concise and 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?

The description lacks detail about the return value (e.g., shape of the schedule objects, available fields), ordering defaults, or constraints. Given no output schema and a simple list tool, more context on what 'budget schedules' are and typical usage would improve completeness.

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% (all three parameters have descriptions). The description adds no extra meaning beyond confirming pagination and the purpose. Baseline 3 is appropriate as the schema already explains limit, after, and fields.

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 identifies the action (List), resource (ad budget schedules), and scope (for the ad account). It also mentions paginated results, which adds specificity and distinguishes it from sibling tools like create_budget_schedule or list_campaigns.

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 versus alternatives. For example, it does not explain if there is a search or filter option elsewhere, or when to use list_budget_schedules vs list_accounts or other list tools. The description only states what it does.

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