bb_file_upload

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

No annotations are provided, and the description only lists techniques without describing the tool's behavior (e.g., whether it sends requests, what it checks, potential destructive actions, or output format).

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?

While the description is very short, it is under-specified to the point of being unhelpful; it reads as a title rather than a functional description, sacrificing information for brevity.

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?

With five parameters lacking any documentation, no annotations, and only a one-line description, the description fails to provide essential context about inputs, outputs, or behavior, making it nearly unusable for an AI agent without external knowledge.

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 coverage is 0% (no parameter descriptions), and the tool description does not explain any of the five parameters (url, proxy, cookie, timeout, auth_token), leaving their purpose and format completely unclear.

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 'File upload bypass detection' and lists specific techniques (extension, MIME, double extension, truncation, .htaccess, SVG), clearly identifying the tool's purpose and differentiating it from sibling tools that target other vulnerabilities.

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 other sibling tools, no exclusions, and no context about prerequisites or typical scenarios.

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