Get realm settings

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

With no annotations, the description carries the full burden. 'Fetch' implies a read-only retrieval, but the description does not disclose behavior on nonexistent realms, permission requirements, or whether any transformation occurs. This is acceptable for a simple getter but not richly transparent.

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 sentence with no filler or redundant restatements. 'Configuration of a single realm' precisely captures the tool's function and scope without wasting words.

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 one-parameter read-only tool without an output schema, 'Fetch the configuration of a single realm' is largely sufficient. It could be slightly more complete by noting the alternative for listing all realms or error behavior, but those are not critical for a basic get-by-name call.

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 already fully describes the only parameter: 'realm' with type string and description 'Realm name'. The description adds no further parameter semantics beyond referencing a single realm, so the baseline score of 3 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 a specific verb ('Fetch') and resource ('the configuration of a single realm'), making both the action and the target unambiguous. It distinguishes itself from siblings like list_realms and get_user by emphasizing 'single' and the realm configuration.

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 phrase 'a single realm' provides clear context for when to use this tool: when a specific realm's configuration is needed. It does not explicitly name an alternative, such as using list_realms for all realms, but the single-vs-list distinction is strongly implied.

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