get_workflow_logs

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

With no annotations, the description carries the full burden and does well: it discloses the streaming/polling nature, the default 10s collection window, and the repeated-call pattern needed to tail a running workflow. It omits auth requirements or any truncation/pagination behavior, keeping it from a 5.

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?

Three sentences, front-loaded with the core action and no wasted preamble. Minor redundancy between "configurable log level and collection timeout" and the following sentence on collection duration.

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?

No output schema exists, so the description must convey return behavior; it explains that logs are streamed/collected over a duration, which is the key framing an agent needs. Adequate for a read-only logging tool, with only minor gaps around log volume or format.

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 100%, so the schema already documents all three parameters and the enum. The description restates "configurable log level and collection timeout" and the 10s default without adding syntax or behavior beyond the schema, matching the baseline 3.

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+resource ("Stream logs from a workflow execution") that is clearly distinct from the get_workflow sibling which retrieves the workflow definition. Purpose is unambiguous, though it does not name any sibling explicitly.

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?

Provides clear usage context ("useful for monitoring workflow progress and debugging") and actionable guidance ("Call repeatedly to continue collecting logs from running workflows"). No explicit when-not or named alternatives, so it stops short of a 5.

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