task_logs

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

Annotations already indicate readOnlyHint=true. Description adds that it returns last tail_lines lines or 'no_log' on missing log/incorrect setup, providing clear behavioral expectations beyond annotations.

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 concise sentences: first states purpose, second states conditions and return value. No unnecessary words, front-loaded for quick understanding.

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 two parameters, annotations, and an output schema, the description covers all essential aspects: what it does, when it works, and what it returns. No gaps for an agent to select and invoke 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 coverage is 0%, so description must compensate. It explains 'tail_lines' as the number of lines to return and implies 'task_id' is the spawned task identifier. While not exhaustive, it adds sufficient meaning for both parameters given the tool's simplicity.

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?

Clearly states 'Read tail of a spawned task's captured stdout/stderr log' – specific verb and resource. Distinguishes from siblings like 'spawn' and 'tasks' by focusing on log retrieval for spawned tasks with capture_output=True.

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?

Explicitly states condition 'Only works for tasks spawned with capture_output=True' and describes fallback 'no_log' for other cases. Does not directly contrast with alternative tools, but the condition is clear enough for an agent to decide when to use.

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