get_job_logs

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool returns raw log text, may be truncated by the caller downstream, and mentions fixture-mode behavior for repo and run_id. It does not discuss auth, errors, or rate limits, but the read-only nature is clearly implied by 'Fetch' and the return description.

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 concise and well-structured: a one-sentence purpose, a compact Args block, and a Returns line. Every part contributes useful information, and the most important purpose statement is front-loaded.

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?

For a simple read-only log-fetching tool with three required parameters and an output schema, the description is largely complete: it explains all parameters and the return value, including truncation. Minor gaps are that it does not specify error behavior or explicitly state authentication requirements, but these are not critical for this tool's simplicity.

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. It does: repo is defined as 'owner/name' and noted as ignored in fixture mode, run_id is explained as needed for the fixture backend, and job_id is identified as the job identifier. This adds meaningful guidance beyond the bare schema types and titles.

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 opens with a specific verb and object: 'Fetch the raw log text for a single job of a workflow run.' This clearly identifies the resource and scope, and distinguishes it from the sibling get_workflow_run, which is run-level rather than job-level.

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 intended context is implied well: use this when you need raw logs for a specific job. However, there is no explicit mention of when to use this tool versus get_workflow_run, and no 'when not to use' guidance. The fixture-mode note is a useful context hint but not a full usage guideline.

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