jumpcloud_tenant_list

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

With no annotations provided, the description carries the full burden. It discloses 'Read-only' and 'Risk: low', and also mentions it may discover scoped users from Postgres and Vault token paths, adding behavioral context. However, it does not detail return format or pagination, but for a read-only discovery tool this is adequate.

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 purpose, and includes only essential guidance. Every sentence earns its place: purpose, usage, and risk. No fluff.

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 read-only list tool with one optional boolean parameter and no output schema, the description covers purpose, usage, risk, and parameter behavior sufficiently. It could add more detail on exact return values, but the low complexity keeps it complete enough.

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 schema has only one boolean parameter (includeUsers) with no schema description. The description's phrase 'optionally discover scoped users' directly hints at the parameter's purpose, compensating partially for the 0% schema coverage. However, it does not explicitly state that includeUsers controls that behavior, leaving some ambiguity.

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+resource structure ('list tenant ids') and clearly marks the operation as 'read-only tenant discovery'. It differentiates from sibling tools by stating that it lists tenants and optionally discovers scoped users, which is unique among the provided siblings.

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?

It explicitly states when to use the tool ('Use to list tenant ids...') and provides a clear exclusion ('Do not use for mutation'). It does not name specific alternatives, but the context of tenant discovery is sufficient to distinguish from mutation or other tools.

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