search_build_output

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

No annotations provided, so description carries full burden. It discloses the tool performs a regex search on raw build output, but omits details like destructiveness, authentication needs, rate limits, or scope of 'latest build'. Adequate for a simple read operation but could be more transparent.

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?

Single sentence, no wasted words. Front-loaded with action and resource. Highly concise while conveying essential purpose.

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 one required parameter and an output schema (not shown), the description is minimal. It lacks context about output format, pagination, what 'latest build' means, and potential constraints. With many sibling tools, more context would help selection.

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 0%, so description must compensate. It confirms pattern is a regex, adding meaning over the schema's 'Pattern' label. However, it does not explain syntax, case-sensitivity, or special characters. Moderate value added.

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 'Regex search across raw build output from the latest build' – a specific verb (search) and resource (raw build output). Differentiates from siblings like search_logs by specifying the source as raw build output and limiting to the latest build.

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?

Implies usage for searching the latest build output, but no explicit guidance on when to use this tool instead of alternatives like search_logs or get_build_errors. No mention of prerequisites or context.

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