sigma_list_tenants_paginated

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

Even though annotations already declare readOnlyHint=true and destructiveHint=false, the description adds that it returns the complete list of tenants, implying automatic handling of pagination. This is valuable context beyond the annotations, though it could further clarify the absence of manual token parameters.

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 three sentences, front-loaded with the action, and every sentence provides relevant information: what it does, pagination model, and return value. There is no redundancy or filler.

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 the simple tool (no parameters, output schema available, annotations present), the description is sufficient. It addresses the pagination mechanism and the complete-list behavior, though it could explicitly state that no page token input is required.

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 zero parameters, so there is no burden on the description to explain them. The mention of nextPageToken is a bit ambiguous given the lack of a parameter, but the 'complete list' clause mitigates this by suggesting the tool handles pagination internally.

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 'List all tenants' with a specific resource and action, and adds the pagination model. It differentiates from offset-based pagination but does not explicitly name the sibling sigma_list_tenants tool, leaving some distinction to inference.

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 explains the cursor-based pagination approach and contrasts it with offset-based pagination, implying the tool's purpose. However, it does not explicitly state when to use this tool over sigma_list_tenants or provide exclusions or alternative scenarios.

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