get_realm_info

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

No annotations are provided, so the description carries full burden. It mentions the optional realm parameter and that a default is used, but does not disclose potential errors, authorization needs, or whether the operation is read-only (implied but not stated). Minimal behavioral insight.

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 concise and front-loaded; the first sentence captures the main purpose. The Args/Returns sections add structure, though partially redundant with schema. It is efficient but not waste-free.

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 tool with one optional parameter and an output schema (presence indicated but content unknown), the description is adequate but not complete. It does not detail the return object's structure or parameter constraints, leaving some questions for the agent.

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?

With 0% schema description coverage, the description compensates by explaining that the realm parameter is optional and uses a default if not specified. This adds meaning beyond the schema's type and default value, though further clarification on valid realm values would improve it.

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 first sentence clearly states the tool's purpose: 'Get information about the current realm.' It specifies the verb and resource, distinguishing it from siblings like get_accessible_realms (which lists realms) and other get_* tools. However, it does not enumerate what information is included, so a small gap for precise purpose.

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 on when to use this tool versus alternatives such as get_accessible_realms, get_realm_events_config, or get_realm_role. The description lacks explicit context or exclusions, leaving the agent to infer usage from the name alone.

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