bb_send

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

No annotations provided; description mentions request/response viewing but fails to disclose side effects, auth needs, or safety profile for a tool that sends network requests.

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 line front-loads purpose efficiently; no wasted words, but could add more without harming 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?

Despite output schema existing, the description is too brief for a tool with 10 parameters; lacks usage scenarios, error handling, or parameter interplay details.

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 only mentions method/headers/body but lacks format, accepted values, or detailed parameter help for the 10 parameters.

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?

Description clearly states manual HTTP request sending with custom method/headers/body and full response viewing, distinguishing it from specialized sibling tools.

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?

Implied usage for custom HTTP requests but no explicit when-to-use or alternatives among siblings like bb_sqli or bb_xss.

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