Server Quality Checklist

Tool Scores

• xploit47A
  4/5.0
  Behavior3/5

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

  With no annotations, the description carries full burden. It explains the tool's reasoning approach (Beam Search/MCTS, scoring, tracking) but does not disclose behavioral traits like whether it executes commands, modifies data, or requires special permissions. It adds context beyond the schema but lacks details on safety or side effects.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The description is two sentences long, front-loaded with the main purpose, and contains no unnecessary words. Every sentence contributes to understanding the tool's function and use.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness4/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  Given the lack of output schema and 8 parameters, the description provides a solid high-level understanding. It covers the algorithms, use case, and key actions but does not describe the output format or how to interpret the returned metrics. It is mostly complete for a reasoning engine.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema coverage is 100%, so baseline is 3. The description does not elaborate on individual parameters beyond the general context of attack steps and strategies. It adds no specific parameter-level meaning that the schema already provides.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description clearly states it is a pentest reasoning engine that breaks down attack paths using Beam Search or MCTS. It specifies the domain (CTF/HTB planning, authorized pentests) and the core actions (scoring, tracking, returning metrics). This is specific and unambiguous, with no sibling tools to confuse.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines4/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description explicitly states when to use it: 'Use for CTF/HTB planning and authorized pentest workflows.' While it doesn't list when not to use it or provide alternatives, the guidance is clear and context-appropriate given the lack of sibling tools.

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