list_scheduling_pages

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

The annotation readOnlyHint already establishes that this is a read-only operation. The description's use of 'List' reinforces that but adds no additional behavioral context, such as pagination, ordering, or what exactly constitutes a 'scheduling page'. No contradiction exists, but the description adds no transparency beyond the annotation.

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?

The description is a single, compact sentence that directly states the tool's function without any superfluous words. It is fully front-loaded and appropriately sized.

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 parameterless list operation, the description is complete. The existence of an output schema covers return value details, and the readOnly annotation covers safety. No further context is necessary to understand the tool's scope.

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 has no parameters (0 params), so the baseline is 4. The description adds no parameter-specific detail, but none is needed since there are no parameters to define.

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 uses a specific verb 'List' and clearly identifies the resource as 'the user's scheduling (booking) pages'. It is unambiguous and, while not explicitly comparing to siblings like get_scheduling_page or create_scheduling_page, the plural 'pages' implies a collection operation distinct from singular actions.

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 guidance on when to use this tool versus alternatives. It only states what the tool does without mentioning scenarios, prerequisites, or trade-offs compared to sibling tools like get_scheduling_page or list_connections.

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