get_task_output

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior. The description adds the important operational constraint that all persisted lines are returned and upstream does not support output pagination, warning that output is unpaginated. It does not discuss auth requirements or task-state prerequisites.

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 one front-loaded sentence plus the endpoint path, with no filler. The no-pagination note earns its place because it affects how the agent should consume the output.

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?

This is a simple read endpoint and annotations carry the safety profile, but there is no output schema and no parameter description coverage. The description covers scope and no-pagination behavior but omits return format and task prerequisites, leaving notable gaps.

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%, so the description must compensate for undocumented parameters. It only echoes project_id and task_id in the endpoint path, adding little meaning beyond the parameter names and their relationship to project and task.

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: get every persisted task log line as structured output. The phrase 'as structured output' distinguishes it from the raw-output sibling get_task_raw_output, so an agent can tell them apart without opening schemas.

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?

The only usage cue is implicit: choose this for structured output rather than raw output. It does not explicitly say when to use it versus get_task_raw_output, nor does it list prerequisites or exclusions.

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