job_log

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's safety is clear. The description adds valuable behavioral context: it streams live while running and extracts rejection lines when present. This goes beyond the annotations and helps the agent understand what to expect. However, it does not mention behavior when the job is not running or error handling, which prevents a higher score.

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 exceptionally concise: two sentences with zero fluff. The main purpose is front-loaded, and the extra rejection-line extraction detail is added without redundancy. Every word earns its place.

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 tool with no output schema, the description covers the core functionality (tail of log, streaming, rejection lines) but leaves gaps: it does not describe the return format (e.g., plain text, structure), behavior when the job finishes, or how to interpret rejection lines. Given the availability of sibling tools like pi_console_log, more clarity on when this is the right tool would improve completeness.

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?

The input schema has 0% description coverage, so the description must explain both parameters. It implicitly explains job_id via 'for a job', but it does not explain the 'tail' parameter at all. The description says 'Tail of the console log' but does not clarify that the 'tail' parameter controls the number of lines returned. This is a significant gap given the lack of schema descriptions.

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 is a tail of the PixInsight console log for a job, with the additional feature of extracting ImageIntegration rejection lines. The verb 'tail' and resource 'console log for a job' are specific, and the scope is unambiguous. It does not explicitly differentiate from sibling tools like pi_console_log, but the 'for a job' qualifier provides some 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?

There is no explicit guidance on when to use this tool versus alternatives such as pi_console_log or job_status. The description implies usage for monitoring a job's log output ('streams live while running') but does not state when not to use it or mention any alternative. This leaves the agent to infer the appropriate context.

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