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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only reveals that RTSP/ONVIF and camera ports are involved, not whether the tool actively scans, what network side effects may occur, or what the response represents. This leaves the agent with an unclear safety and behavior profile.

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 text is very short and each phrase contributes some technical scope, so there is no wasted wording. However, it functions more as a label than as an instruction, and the under-specification prevents it from earning a higher structure score.

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 network-exposure tool with no annotations and an undocumented q parameter, the description is materially incomplete. It lacks the expected target format, input semantics, and any safety notes, and the output schema cannot compensate for those gaps.

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 single parameter q has 0% schema description coverage, and the tool description never mentions it. The phrase 'per-target' vaguely implies a target is needed, but the format, meaning, and optionality of q are entirely unexplained, so the agent cannot determine how to populate it correctly.

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 names a specific domain — RTSP/ONVIF plus camera-port exposure — and indicates the operation is per-target, so it is not a bare tautology. However, 'Exposure' is a noun phrase rather than an explicit verb like 'scan' or 'detect', leaving the exact action ambiguous. It also does not distinguish itself from sibling scan-oriented tools beyond the camera-specific vocabulary.

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?

There is no when-to-use guidance, no mention of alternatives, and no exclusions. The only hint is 'per-target,' which suggests the tool acts on a single target but gives no guidance on how to choose this over portscan or other discovery tools.

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