find_assets_not_scanned_since

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

No annotations are provided, so the description carries the burden. It usefully clarifies the semantics of "not scanned since" (based on latest known scan result), but does not state that it is a read-only query, mention permissions, pagination, or any limits on the result set.

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 tightly written sentences with the defining condition front-loaded and a compact example that resolves ambiguity about the argument. No wasted text.

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?

An output schema exists, so return values need no explanation. For a simple one-parameter query tool the description is largely sufficient, though the absence of annotations means the missing read-only/permission context is a minor gap.

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 coverage is 0% for the single 'days' parameter, so the description must compensate. It does explain that the threshold is measured in days via 'older than the specified number of days' and reinforces it with the find_assets_not_scanned_since(7) example, but omits the default of 7 that exists in the schema.

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 (find) plus resource (Nessus hosts) and the exact selection criterion (latest known scan result older than N days). It is clearly distinguishable from sibling read tools like list_nessus_scans or get_nessus_scan_history, though it never names those siblings explicitly.

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 use case (locating stale or unscanned assets) is implied by the condition in the description but never stated as guidance, and no alternative sibling tool is offered for related queries. Adequate but leaves routing inference to the agent.

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