pentest_burp_import

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

No annotations are supplied, so the description carries the full burden. It does disclose the key behavioral fact that issues become findings (a write/mutation) and that no live API is needed, but it says nothing about duplicate handling, whether existing findings are overwritten, or what happens on a malformed XML file.

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?

Two short sentences, front-loaded with the action and resource, with the practical export hint second. Nothing is wasted.

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?

For a two-parameter mutation tool with no annotations and no output schema, the description leaves the 'record' flag, the return value (e.g., count of imported findings), and duplicate/error behavior undocumented. An agent could call it, but not confidently predict the outcome.

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 description coverage is 0% for both parameters, and the description adds no meaning: 'path' is only inferable as the XML file location, and 'record' (default true) is never explained at all. With zero coverage in the schema, the description needed to compensate and does not.

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 gives a specific verb and resource ('Import a Burp Suite XML report/export and convert the issues into findings'), which is enough to tell it apart from pentest_zap_import and pentest_burp_api by product and by action. It stops short of naming a sibling explicitly, so it lands just below the top mark.

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?

'Works with any Burp edition (Report -> XML export). No API required.' describes a prerequisite and the export path, not when to choose this tool over pentest_burp_api, pentest_zap_import, or pentest_add_finding. Usage is only implied by the import/convert framing.

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