tools_assetfinder

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

No annotations are provided, so the description carries the full burden. It only says 'Execute Assetfinder' without disclosing what the tool does (e.g., runs a command line tool, returns subdomains), side effects, or output format. Behavioral details are missing.

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 very short and front-loaded with the purpose. It efficiently conveys the tool's function, though it could be slightly more detailed without losing conciseness.

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 complexity (runs an external tool) and the lack of output schema details and annotations, the description is incomplete. It does not explain what Assetfinder does, what the output looks like, or prerequisites.

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?

The schema has 0% description coverage. The description adds brief meaning for 'domain' ('Target domain') and 'additional_args' ('Extra assetfinder arguments'), but the latter is vague. It provides some additional context beyond 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 states 'Execute Assetfinder for asset discovery,' which is a specific verb and resource. It clearly indicates the tool runs Assetfinder for asset discovery, but it does not differentiate from sibling tools like tools_amass or tools_subfinder.

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?

There is no guidance on when to use this tool versus alternatives. Among many sibling tools with similar purposes (e.g., tools_amass, tools_subfinder), the description provides no context for selection.

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