get_task_log

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

No annotations are provided, so the description carries the full burden. It discloses the underlying API (GET), explains the four detail_level outputs, lists response fields (logId, status, messages, children), and enumerates possible status values. This is exceptionally transparent.

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 description is well-structured with sections and bullet points, but it is quite verbose for a simple read tool. There is redundancy between 'What you'll get' and 'Optional parameters' both explaining detail_level, and the 'Use cases' section largely repeats the 'Use this tool when' list.

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?

There is no output schema, but the description compensates thoroughly by detailing response contents, status values, example queries, and use cases. It gives an AI agent everything needed to select and invoke the tool correctly.

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 documentation covers all 3 parameters with descriptions, so the baseline is 3. The description adds extra value by explaining where log_id comes from, providing example space_id values, and elaborating on the detail_level enum beyond the schema's bare enumeration.

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 uses a specific verb 'Get' and identifies a precise resource: 'detailed information about a specific task execution in SAP Datasphere'. It clearly distinguishes this from sibling tools like get_task_status and get_task_history by focusing on a single log and referencing run_task_chain.

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?

Provides explicit 'Use this tool when' scenarios (checking status, investigating failures, viewing logs, monitoring progress). It also indicates log_id provenance from run_task_chain or get_task_history. However, it lacks explicit when-not-to-use guidance or named alternatives like get_task_status.

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