Get logs for an execution

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

With no annotations provided, the description carries the full burden. It discloses that logs are structured, chronological, and filterable by several criteria, but it does not describe the return format, pagination behavior, or any read-only guarantees. This is a moderate level of disclosure, similar to the TDQS 4.3 example.

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 a single, well-structured sentence that front-loads the core action and resource, then lists optional filters. There is no redundant information or filler.

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?

The tool has 8 parameters, no output schema, and no annotations. The description explains what the tool does and some filters, but it does not describe the return structure, pagination, or any edge-case behavior. Given the complexity and lack of output schema, this is incomplete.

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 only 38% (3 of 8 parameters). The description mentions filters for hypothesis, level, time range, and text search, which maps to some parameters, but it omits the meaning of limit, offset, and executionId. The description partially compensates for low coverage but leaves key parameters unexplained.

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 uses the specific verb 'Fetches' with a clear resource: 'structured logs recorded for a single execution'. It also specifies ordering and optional filters, making it distinct from sibling tools like execution_list or execution_compare.

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 description clearly implies the tool is for retrieving logs for one execution and lists filter options, but it does not explicitly state when to use it over alternatives or provide exclusions. The context of sibling tools suggests a clear use case, so a 4 is appropriate.

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