zdx_list_cloudpath_probes

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds the useful 'full records' behavior and the downstream dependency, but it does not disclose pagination, rate limits, or other caveats beyond the provided annotations.

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 two short paragraphs with the core action front-loaded and the prerequisite stated immediately. Every sentence contributes either purpose, workflow, or safety context, with no filler.

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 simple list tool, the description covers the resource, scope, default 'full records' behavior, and a concrete downstream consumer. However, with no output schema and an unexplained optional `since` parameter, it is not fully self-contained, though it is strong overall.

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 description coverage is only 25%; `query` is well explained in the schema, and the prose description implies the roles of `device_id` and `app_id` with 'for an app on a ZDX device.' However, `since` is left undocumented in both the description and schema, so the description only partially compensates for the coverage gap.

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 opens with a specific verb and resource: 'List cloud-path probes for an app on a ZDX device (full records).' This clearly distinguishes the tool from sibling ZDX list/get operations and states the scope and output mode.

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?

It gives explicit workflow guidance: 'Call this BEFORE `zdx_start_deeptrace` to obtain the `cloudpath_probe_id` the deep-trace payload needs.' This explains when the tool is needed, though it does not name exclusionary alternatives or explicit when-not-to-use cases.

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