get_task_logs

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

No annotations are provided, so the description carries the full disclosure burden, and it says nothing beyond the name. It does not state the return shape, whether results are paginated or truncated, whether a task identifier is needed, or how far back logs go. Only the weak implication of read-only behavior from "Get" is conveyed.

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 phrase is front-loaded and contains no filler, so it is not verbose. But at four words it is under-specified rather than concise; nothing beyond the tool name is communicated.

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 annotations, no output schema, and no parameters, the description is the only source of meaning and it supplies none. An agent still cannot determine which task's logs this returns or under what conditions to call it.

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 input schema declares zero parameters and 100% coverage, so there is nothing for the description to explain or compensate for. The baseline for a parameterless tool applies.

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 verb and a resource ("Get" + "task logs"), so the basic operation is clear. However, it never defines what a "task" is in this product, and with siblings like list_operation_logs, list_system_logs, get_container_logs, and get_executing_task_count in the same namespace, an agent cannot tell which log source this returns.

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 statement of prerequisites, and no routing to alternative log tools. Given the cluster of near-identical log/list siblings, the absence of any disambiguation is a real gap rather than a harmless omission.

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