List realms

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

Since no annotations are provided, the description carries the burden of explaining behavior, and it does so by mentioning credential-based visibility and allowlist filtering. The 'list' verb also communicates a read-only intent, though it does not explicitly address error cases or formatting.

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 two short sentences, front-loaded with the action and then embedding the filtering qualifier. Every word adds value and there is no redundant information.

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 parameterless list operation without an output schema, it completely conveys what will happen, who it applies to, and how the allowlist affects the result. No further detail is required for confident invocation.

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?

There are zero parameters, so the schema leaves nothing to explain. The description's mention of visibility and allowlist behavior compensates for the lack of any structured parameters, making this baseline-4 situation fully comfortable.

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 a specific verb and resource: 'List all realms'. It also includes the scope 'visible to the configured credentials' and the allowlist filter, making its purpose precise and distinct from get_realm and list_users.

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 gives solid contextual guidance, saying this operation returns all visible realms while filtering out ones outside the allowlist. It does not explicitly contrast with get_realm or other siblings, but the 'list all' scope makes the intended use clear.

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