sigma_list_tenants

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

The description claims to 'List all tenant organizations', which directly contradicts the openWorldHint annotation indicating results may not be exhaustive. Aside from this, it adds no behavioral detail beyond what annotations already provide, such as pagination, permissions, or result set limitations.

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 concise sentence, front-loaded with the action and resource, with a parenthetical context qualifier. Every word earns its place, and there is no redundant or filler text.

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 tool's simplicity (zero parameters, output schema present, read-only annotations), a minimal description is mostly sufficient. However, the openWorldHint contradiction leaves ambiguity about whether the result set is complete, and the sibling sigma_list_tenants_paginated is not mentioned, making the description less complete than it could be.

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 tool has zero parameters, and the input schema is empty. Per the baseline for zero-parameter tools, a score of 4 is appropriate because there are no parameter semantics for the description to clarify.

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 resource ('tenant organizations'), with a context qualifier ('for multi-tenant deployments'). It clearly states what the tool does, but it does not explicitly differentiate it from the sibling tool sigma_list_tenants_paginated, even though 'all' hints at a non-paginated variant.

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?

No guidance is provided on when to use this tool versus alternatives such as sigma_list_tenants_paginated or sigma_get_tenant. The phrase 'for multi-tenant deployments' offers some context but no exclusions, prerequisites, or explicit alternative recommendations.

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