list_schedules

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

Annotations already provide readOnlyHint, idempotentHint, openWorldHint. The description adds valuable context: paginated skeletons with default limit 100, ability to pass cursor/fields/filter/verbose, caching behavior (cursor staleness), and the plan-gating. 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: first explains core behavior, second provides usage guidance vs. sibling. No fluff, every sentence earns its place. Front-loaded with most important info.

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 7 parameters, no output schema, and sibling context, the description is complete. It explains return shape (skeleton with specific fields), pagination with cursor, and filtering options. No gaps.

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 baseline is 3. The description adds meaning beyond schema: explains 'verbose' returns full schedule objects with intervals, 'fields' opt-in without full verbose, and 'filter' supported keys. This enriches understanding.

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 returns business-hours schedules as paginated skeletons with specific fields (id, name, time_zone, updated_at). It distinguishes from the sibling tool `list_business_hours` by explaining that tool composes intervals and holidays, which the list alone doesn't cover.

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?

Explicitly tells when to use this tool vs. `list_business_hours`: 'For "what are the actual business hours?" call list_business_hours with a schedule_id, it composes intervals + holidays, which the schedule list alone doesn't cover.' Also mentions it is plan-gated (Professional+).

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