pentest_assets

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

No annotations are supplied, so the description carries the full behavioral burden. 'Return' implies a read, but nothing is said about whether it requires a loaded engagement, whether it triggers any scanning, what happens when the inventory is empty, or whether results are cached/aggregated across sessions.

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?

A single front-loaded sentence with the action first and the returned contents enumerated; no filler, no redundancy.

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?

With no output schema, the description is the only signal of what comes back, and it does name the three categories of assets. However, for a zero-param aggregate tool it omits scope (per engagement? per target?) and the shape/grouping of the returned inventory.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misdescribes the empty argument object.

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?

States a specific verb ('Return') and resource ('aggregated asset inventory') and enumerates contents: hosts, services, technologies. An agent can distinguish it from scanning siblings like pentest_recon_portscan or pentest_osint_shodan, though the description never says the inventory comes from prior engagement data rather than fresh discovery.

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 when-to-use guidance, no prerequisites (e.g., must an engagement be loaded?), and no named alternatives. The agent must infer that this is a retrieval/summary step rather than a collection step, and must guess how it relates to pentest_attack_surface or pentest_list_findings.

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