get_task_instance_logs

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

Annotations are absent, so the description bears the full burden of disclosure. It offers no behavioral details such as log format, truncation, or authentication requirements. The minimal description fails to inform the agent about the tool's behavior beyond the literal meaning.

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 very concise (one sentence), which is positive, but it is not structured with sections or bullet points. It is appropriately short but lacks the structure that would make it more 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?

Given the tool has 4 parameters and an output schema, the description is too sparse. It does not explain the role of try_number, the nature of logs returned, or any context like whether logs are limited. The output schema exists, so return values need not be described, but the remaining context is insufficient.

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%, yet the description does not explain any of the four parameters. It only mentions 'specific task instance,' which loosely connects to required params but provides no semantics for try_number or the required fields. The description adds negligible value beyond the schema.

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 clearly states it retrieves logs for a specific task instance, which is a verb+resource pattern. However, it does not differentiate from sibling tools like get_task_instance_details or get_xcom_entry, which have distinct purposes. The purpose is clear but lacks sibling distinction.

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?

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, scenarios, or exclusions. It provides no context for tool selection.

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