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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so safety is covered; the closing 'Changes nothing.' restates that. The description earns credit beyond the annotations by disclosing the response surface (plan, siteIds, limits, per-site deploy/submission/domain/bandwidth usage, upgrade path) and by implying an authenticated-connection requirement, which matters because there is no output schema.

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?

One long but front-loaded sentence: identity and scope come first, the contents in a parenthetical list, the safety note last. Every clause carries information, though the dense list could be broken for faster scanning and 'Changes nothing.' duplicates the annotations.

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?

With no output schema, the description carries the return-value burden and does so thoroughly, covering plan tier, site inventory, limits, and usage metrics. The only real gap is edge behavior (what is returned if the connection is unauthenticated or the account has no sites), which is minor for a zero-argument read.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly presents this as a no-argument call scoped implicitly to the signed-in connection.

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 (shows) and resource (the RunLite account for this connection) and then enumerates the exact contents: plan, sites with siteIds, plan limits, usage counters, and the next plan up. That is clearly distinct from sibling readers such as get_site, get_form, or get_submissions, which each target one object.

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 rather than stated: an agent can infer this is the account-level overview to call before working with sites, and 'this month's usage against the plan' hints at capacity checks. However, there is no explicit when-to-use, no when-not-to-use, and no named alternative (e.g. get_site for one site's detail).

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