zdx_get_web_probes

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' reinforces this. The description adds valuable context: the tool returns full records and its output (web_probe_id) is needed for a subsequent operation. This goes beyond what annotations provide, though it does not detail pagination or rate limits.

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 sentences with no wasted words. First sentence states purpose and read-only nature; second provides usage guidance. Information is front-loaded and efficient.

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 tool's simplicity (list operation with two required IDs and an optional filter), the description covers purpose and usage well. However, it omits details about the return format or what fields are included in 'full records', and the 'since' parameter remains unexplained. With no output schema, more descriptive context would help.

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 description does not explain any parameters. Input schema has 4 parameters with only 25% description coverage (query has description). The 'since' parameter lacks any schema or description explanation. The description should compensate for low schema coverage but does not, leaving parameter semantics unclear.

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?

Clearly states 'List web probes for an app on a ZDX device (full records)'. The verb 'list' combined with the resource 'web probes' precisely defines the operation. The phrase 'full records' adds specificity. It is distinct from sibling tools that list other entities (e.g., devices, alerts).

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?

Explicitly instructs 'Call this BEFORE `zdx_start_deeptrace` to obtain the `web_probe_id` the deep-trace payload needs.' This provides clear when-to-use guidance and explains the purpose of the returned data, differentiating it from other list tools.

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