Browse Log Files

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

Discloses important behaviors beyond annotations: path semantics (no path lists top-level, trailing '/' lists subdir, file path fetches content), a 512KB size limit, max_lines behavior, and direct_log_url skipping build metadata fetch. These details are essential for correct invocation.

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 compact and well-structured: a one-sentence overview, a short mode breakdown, and a bulleted Args list. Every sentence provides necessary information without redundancy.

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?

Covers all functional modes, parameter semantics, size limits, and alternatives. With an output schema present, return values are already specified, so the description is complete for tool selection and invocation.

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?

Despite 0% schema description coverage, the description explains every parameter (uuid, tenant, path, url, max_lines, direct_log_url) with concrete meaning and example format. It fully compensates for the schema's lack of description and adds practical context.

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-resource pair: 'Browse or fetch files from a build's log directory.' It clearly explains the three modes (top-level listing, subdirectory listing, file content fetch) and distinguishes itself from get_build_log by mentioning it as an alternative for filtered reads.

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?

Explicitly states when to use get_build_log instead for filtered reads, and provides usage patterns for path handling and direct_log_url. It does not exhaustively cover all sibling alternatives, but the guidance is clear and practical.

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