Search Bugcrowd VRT

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is clear. The description adds important context about results being a technical baseline and taxonomy being untrusted data, which is valuable beyond annotations.

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 brief (two sentences plus security warnings) and front-loads the core purpose. However, the first sentence could be clearer (e.g., 'terminal' is ambiguous).

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 4 optional parameters with no parameter descriptions and an existing output schema, the description fails to document query syntax, pagination limits, or result format. It is incomplete for search tool guidance.

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?

With 0% schema description coverage, the description must compensate for missing parameter details but adds none. It does not explain what 'query', 'priority', 'limit', or 'offset' mean in this specific VRT context, relying entirely on 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 searches the Bugcrowd VRT, referencing a specific version (1.19), but it does not sufficiently distinguish it from sibling tools like 'vuln_search_cves' (which also searches vulnerability-related data).

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?

The description provides no guidance on when to use this tool versus alternatives like 'vuln_search_cves' or 'vuln_get_cve'. It only includes warnings about data authorization and taxonomy, not usage differentiation.

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