assess_report_quality

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

No annotations are provided, so the description carries full burden. It mentions the tool is based on historical patterns but does not disclose behavioral traits such as whether the assessment is deterministic, if any data is stored, or if there are rate limits. It lacks depth for a predictive tool.

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 two sentences long and front-loaded with the core purpose. Every word earns its place, and there is no extraneous information.

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 being a relatively simple tool with 5 parameters, the description does not specify the output format (e.g., a score, classification, or textual assessment). Without this, an AI agent cannot fully understand how to use the result, making it incomplete.

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 input schema covers 100% of parameters with descriptions. The description adds only a generic instruction to provide vulnerability details, which does not improve understanding beyond the schema. Baseline score of 3 is appropriate.

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 evaluates a bug bounty finding's likelihood of acceptance or rejection, specifying the action 'evaluate' and resource 'potential bug bounty finding'. This distinguishes it from sibling tools like browse_knowledge_base and get_bounty_reports which are retrieval-oriented.

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 usage by saying 'Provide vulnerability details to get an assessment' but does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria. It offers no guidance on prerequisites or context.

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