anjian_import_web_evidence

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description usefully discloses that only sanitized metadata within authorized scope is saved and explicitly states what is NOT saved (cookies, tokens, bodies), which is valuable privacy/security context for an agent deciding to use this tool on sensitive data.

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 a tight two-clause sentence that packs purpose, scope constraint, and data-handling disclosure without redundancy. Every word earns its place and it is clearly front-loaded.

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 2-parameter import tool with no annotations and no output schema, the description covers the main behavioral contract (what's imported, what's stripped) well. However, given 0% param coverage and no mention of return values, file format details, or error scenarios, it's adequate but has meaningful gaps for a tool handling import.

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%, so the description must compensate. The description mentions file formats (Burp XML/HAR) but does not explain either parameter: assessment_id's format/role or file_path's expected path type/location. Both required parameters are undocumented beyond their titles, leaving the agent guessing about acceptable values.

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 states a specific verb+resource ('导入 Burp XML 或 HAR') and clarifies the scope by noting it only saves sanitized metadata within authorized scope. However, it doesn't explicitly distinguish this from the sibling anjian_import_pcap, though the file-format mention (Burp XML/HAR) implies the difference.

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 is silent on when to use this vs anjian_import_pcap or other tools. The input formats (Burp XML/HAR) imply web-traffic import use, and the authorization-scope constraint implies prerequisites (authorized targets), but no explicit when/when-not guidance or alternative naming is given.

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