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

The annotations already establish this is a safe, read-only, non-destructive, closed-world operation, so the bar is lower. The description adds one genuinely new behavioral fact – the endpoint is undocumented and may change without notice – which is useful for an agent assessing reliability, but it omits anything about log scope, size, or pagination.

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 short sentences, purpose front-loaded first, with a caveat second. Nothing is padded or redundant.

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 and only one parameter, the definition is minimally serviceable, but it never indicates what the returned logs contain or how they are scoped (per stage, per run). The stability warning is a nice touch but does not compensate for the absent return expectations.

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 coverage is 100% for the single stageId parameter, so the schema already carries the parameter documentation; there is only a minimal 'The stage ID' description. The tool description adds no format or sourcing detail beyond the schema, making the baseline 3 appropriate.

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 (Retrieve) and resource (logs for a HyperExecute stage), so the purpose is unambiguous. However, it does not distinguish itself from the closely related sibling getHyperExecuteTaskLogs or clarify its relationship to getHyperExecuteStage/getHyperExecuteStageTasks, leaving an agent to guess which log-retrieval tool applies at which granularity.

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 many sibling log and stage tools such as getHyperExecuteTaskLogs or getHyperExecuteJobArtifacts. The only added sentence concerns API stability, not selection criteria or prerequisites.

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