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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description does add one genuinely useful behavioral trait beyond the annotations: the '(UNDOCUMENTED - may change without notice)' caveat warns that output/behavior is unstable. It still says nothing about log availability timing, size, or format, so it is adequate but not rich.

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 clauses with zero padding, and the core purpose is front-loaded ahead of the caveat. Nothing is repeated from the title or schema.

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 single-param read tool with full schema coverage and annotations, the description covers the essentials, and no output schema exists so return values need not be explained. It is still missing the sibling disambiguation and any note on when logs become available, which leaves a real gap in a crowded log-retrieval family.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents 'taskId'. The description adds no syntax, format, or sourcing detail (e.g. where to obtain a task ID) beyond what the schema provides, matching the baseline 3 for schema-covered params.

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 and resource ('Retrieve logs for a HyperExecute task'), so the agent knows the operation. However, it does not distinguish itself from close siblings such as getHyperExecuteStageLogs or getHyperExecuteTask, and does not clarify whether logs are task-scoped or stage-scoped, which is the key ambiguity in this family.

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 when-to-use guidance, no mention of prerequisites (e.g. whether the task must be completed or still running), and no routing to alternatives like getHyperExecuteStageLogs when stage-level logs are wanted. The agent must infer usage entirely from the name.

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