list_budget_schedules

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

With no annotations provided, the description carries the transparency burden. It discloses pagination ('Returns paginated results') and conveys read-only intent through 'list', but does not mention authentication requirements, potential side effects, or how the ad account is determined. The 'for the ad account' phrase is vague about which account is used.

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, front-loaded with the action and resource, with no filler or redundant information. The description is efficiently structured and immediately understandable.

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 simple list tool with no output schema and no annotations, the description covers the core purpose and pagination behavior. It lacks details about default returned fields or response structure, but the schema handles parameter semantics. Overall, it is reasonably complete for an experienced agent.

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?

The input schema covers 100% of the parameters (after, limit, fields) with descriptions, so the baseline is 3. The description's mention of pagination adds minimal semantic value beyond the schema's own descriptions of 'after' and 'limit'.

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 action ('List') and the resource ('ad budget schedules') scoped to 'the ad account', distinguishing it from sibling tools like create_budget_schedule, update_budget_schedule, and delete_budget_schedule. It also mentions 'Returns paginated results', adding a key behavioral detail.

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 provides no explicit guidance on when to use this tool versus alternatives. Usage is implied by the verb 'list' and the resource, but no exclusions, alternative references, or specific contexts are mentioned beyond 'for the ad account'.

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