get_zen_output

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

Discloses that the tool retrieves recent output from a capture file and mentions the content types (stdout/stderr, MOZ_LOG, etc.). However, with no annotations, it lacks details on side effects, permission needs, or performance implications.

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?

Two sentences, each serving a distinct purpose: first defines the tool's function, second guides usage. No redundant information.

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?

Adequate for a simple retrieval tool with well-documented parameters, but lacks description of output format or default behavior when no filters are applied, especially since there is no output schema.

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?

All three parameters are fully described in the schema (100% coverage), so the description adds little beyond summarizing the filtering functionality. This is the baseline for high schema coverage.

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?

Clearly states the verb 'Retrieve' and the resource 'Zen output (stdout/stderr including MOZ_LOG, warnings, crashes, stack traces)', differentiating it from sibling tools like get_zen_info or get_network_request.

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?

Briefly suggests using filters to focus on specific content, but does not explicitly state when to use this tool versus alternatives or provide contexts where it is inappropriate.

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