get_pipeline_job_run_log

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation (implied by 'Get'), what format/log-level the logs are in, if there are rate limits, authentication needs, or pagination for large logs. The description is minimal and misses key operational context.

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 front-loaded with the main purpose in the first sentence. The second sentence reinforces the scope but could be integrated more efficiently. No wasted words, though it could be slightly more structured for clarity.

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 no annotations and no output schema, the description is incomplete. It doesn't explain the return format (e.g., text, JSON, structured logs), error conditions, or behavioral traits like whether logs are streamed or truncated. For a log retrieval tool with 4 required parameters, this leaves significant gaps for an AI agent.

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 100%, so parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying the tool retrieves logs for a specific job, which is already clear from parameter names like 'jobId'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the verb 'Get' and resource 'execution logs of a pipeline job', specifying it retrieves log content for a specific job in a pipeline run. It distinguishes from siblings like 'get_pipeline_run' or 'list_pipeline_job_historys' by focusing on logs, but doesn't explicitly differentiate from similar tools like 'get_machine_deploy_log' or 'find_task_operation_log'.

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 is provided. The description mentions retrieving logs for a specific job, but doesn't specify prerequisites (e.g., job must be completed), or contrast with other log-related tools like 'get_machine_deploy_log' or 'list_change_order_job_logs'.

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