get_build_log

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

The tool has no annotations, placing full burden on the description. It mentions two output modes (summary/full) and smart truncation but lacks details on side effects, required permissions, or what constitutes 'smart' behavior.

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 two concise sentences with no wasted words, efficiently conveying the core functionality.

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 the number of parameters and lack of output schema, the description adequately covers the tool's behavior (summary vs full, filtering). However, it could hint at the output format (e.g., raw text).

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 the schema already provides parameter details. The description adds no extra meaning beyond mentioning format defaults, which are also in the schema.

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 tool retrieves a build log with smart truncation and filtering, distinguishing it from sibling tools like search_log or analyze_build_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 explicit guidance on when to use this tool versus alternatives like search_log or tail_log_live. The description only implies usage through the tool's name and basic functionality.

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