training.import

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action ('Import') but doesn't describe what 'import' entails—e.g., whether it creates new records, overwrites existing data, requires authentication, has side effects like database writes, or handles errors. This is inadequate for a tool with 9 parameters and potential data mutation.

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 single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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?

Given the complexity (9 parameters, no annotations, no output schema), the description is insufficient. It lacks details on behavior, output format, error handling, or integration with sibling tools, leaving significant gaps for an agent to use this tool effectively in a security training context.

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 schema description coverage is 100%, providing clear documentation for all parameters. The description adds no additional parameter semantics beyond implying 'source' values ('HTB or PortSwigger labs'), which partially overlaps with the schema's enum. This meets the baseline for high schema coverage but doesn't enhance understanding.

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 action ('Import') and resource ('training data'), specifying the sources ('HTB or PortSwigger labs'). It distinguishes from siblings like 'training.import_htb' and 'training.import_portswigger' by being more general, but doesn't explicitly differentiate from 'training.import_all' or 'training.extract_from_writeup', leaving some ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, compare to sibling tools like 'training.import_all' or 'training.extract_from_writeup', or specify scenarios for use, leaving the agent to infer context from the tool name alone.

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