bb_secrets

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

No annotations provided. The description only mentions 'detection' but does not disclose how the tool operates (e.g., network requests, page scanning, side effects). It lacks critical behavioral details for a security scanner.

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 one concise sentence, but it is too brief and omits important details. It could be structured to include more context without being lengthy.

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 6 parameters and no schema descriptions, the description fails to provide sufficient context for usage. Output schema exists but is not referenced. The tool's complexity demands more comprehensive explanation.

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). The description does not explain any of the 6 parameters (url, proxy, cookie, timeout, check_js, auth_token). It adds no value 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 clearly states it detects sensitive information leaks (Key/Token/Password/Internal address/Comment) and specifies 20 patterns. This distinguishes it from sibling tools which focus on other vulnerabilities like SQLi, XSS, etc.

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 implies use when scanning for secrets, but does not explicitly state when to prefer this over siblings or when not to use it. No exclusions or alternatives are provided.

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