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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is fully covered. The description adds a useful inventory of what is returned, but says nothing about authorization requirements, whether results vary by environment, or error behavior for unconfigured companies.

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 definition is a single front-loaded sentence with no filler, but it is essentially a verbatim restatement of the title and adds almost no information beyond it. It is concise without being informative.

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 two-parameter read tool with no output schema and zero-described parameters, the description should explain the company/environment semantics and how this differs from configure. Instead it only lists result categories, leaving the required call arguments entirely undocumented.

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?

Schema description coverage is 0%, and the description never mentions either required parameter. It does not explain that 'company' is a company UUID or that 'environment' selects staging versus production, even though the environment enum materially changes the data returned.

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 states a specific read operation and enumerates the resources returned (runtime connection, capability switches, pilot cases, investigation setting, configuration history). That is clear enough to distinguish it from most siblings, though it never mentions the closely related summer_runtime_connection_configure tool, so the boundary between reading and configuring is left implicit.

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?

There is no guidance on when to use this tool versus the sibling summer_runtime_connection_configure, nor any prerequisites such as permissions or whether the company must already have a runtime configured. The only implied usage is 'read these runtime settings', which an agent could infer 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.