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

readOnlyHint=true already covers the safety profile, and the description adds real value by enumerating the returned fields (name, subdomain, time zone, URL, logo, theme colors), which matters because there is no output schema. The phrase 'connected site' usefully clarifies that no siteId parameter is needed, resolving the apparent mismatch with the /v1/sites/{siteId} endpoint.

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?

Two sentences, zero waste, with the substantive content (what fields come back) front-loaded before the API endpoint reference.

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 zero-parameter read tool with no output schema, the field enumeration supplies nearly everything an agent needs to decide whether to call it. Only minor gaps remain (no mention of error behavior if the site connection is misconfigured), which are not essential for 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?

Zero parameters, so the baseline is 4. The description helpfully explains that the target site is implicit ('the connected site'), which is the only semantic question the empty schema raises.

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?

States a specific verb+resource ('basic information about the connected LeagueApps site') and enumerates the fields returned, so an agent knows exactly what it gets. It is distinguishable from siblings like get_location/get_program by resource, though it doesn't explicitly name those alternatives.

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?

Usage is implied — call this to fetch site-level metadata such as time zone or subdomain before other operations — but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer that this is the site-level counterpart to the location/program getters.

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