vorion_tenant_list

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

With no annotations provided, the description carries full burden. It discloses admin-only access, the API key requirement via VORION_API_KEY, and the exact return fields. It does not mention rate limits, pagination, or error behavior, but covers the most relevant behavioral traits for a list operation.

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?

Four short sentences, each adding value: purpose, access restriction, return contents, and authentication method. 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?

For a simple zero-parameter tool with no output schema, the description is complete: it explains what it does, who can use it, what it returns, and how to authenticate. Lacking pagination details is not critical for a tenant list.

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, so the description correctly avoids parameter detail. With 100% schema coverage trivially satisfied, the baseline 4 for zero-parameter tools applies.

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 the specific verb 'List' with the resource 'all tenants' on the 'Cognigate Runtime', clearly distinguishing it from sibling tools like vorion_tenant_whoami (single tenant) and vorion_tenant_audit_tail (audit logs).

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 clearly states 'Admin-only' and 'Requires an admin-role API key', giving explicit access context. It does not name alternatives or exclusions, but the scope 'all tenants' implies enumeration, differentiating it from other tenant-related tools.

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