aflpp.detect_build_system

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions the heuristic nature, but does not state whether the operation is read-only, what side effects it might have, or any environmental prerequisites. This is insufficient for an agent to understand the tool's safety profile.

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 sentence of 11 words, front-loaded with the action and object. It contains no fluff and earns every word, making it highly efficient for an agent to parse.

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 no output schema and minimal parameter schema, so the description should explain what is returned or how the result is presented. It does not, leaving the agent without critical information about the output or error behavior. The one-sentence description is inadequate for full contextual understanding.

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 the description must compensate. It says 'project path' but this only mirrors the parameter name project_path without adding detail. No format, constraints, or examples are given, leaving the agent guessing about acceptable input types.

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 detects a build system for a given project path, using the verb 'detect' with a specific resource. It is distinct from sibling build tools like build_instrumented and build_cmplog_variant, which actually perform builds. However, it does not define what a 'build system' is or what the output looks like, so it is slightly vague.

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 guidance is given on when to use this tool versus alternatives. The description only says what it does, not why or when it should be chosen. It implies a pre-build step, but there is no explicit context or exclusions, leaving the agent to infer usage.

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