list_appointment_outcomes

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

With no annotations provided, the description carries behavioral disclosure itself. It goes beyond the schema by explaining that the default limit is intentionally set to 100 for bulk use cases and by describing how to continue paginating via _metadata using offset or cursor-based next. This is meaningful behavioral context, though it stops short of describing response structure or error behavior.

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 compact and front-loaded with the core purpose. Both sentences earn their place: the first states the operation and default behavior; the second provides actionable pagination guidance. There is no redundant or filler content.

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 list endpoint with no output schema and no annotations, the description covers the important operational details: endpoint, intentional default, and pagination loop. It could be more complete by briefly indicating the response shape, but the provided guidance is sufficient for an agent to call the tool correctly and handle paging.

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 description coverage is 100%, so the baseline is 3. The description adds useful workflow context around pagination and the limit default, but it does not add substantially new meaning to individual parameters beyond what the schema already documents.

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 verb and resource: 'List appointment outcomes' with the endpoint GET /appointmentOutcomes. It distinguishes itself concept from sibling create/get/update operations, though it doesn't explicitly contrast with those sibling tools.

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 gives clear context that bulk requests are the common case and explains default pagination behavior. However, it does not explicitly state when to use this tool versus get_appointment_outcome or create_appointment_outcome, leaving the usage distinction to be inferred from the tool name.

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